Triple
T12740544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Grudusk |
E304476
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Grudusk |
E1001206
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Grudusk | Statement: [Gmina Grudusk, hasSettlement, Grudusk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grudusk Context triple: [Gmina Grudusk, hasSettlement, Grudusk]
-
A.
Grudusk
chosen
Grudusk is a village in north-central Poland that serves as the administrative center of the surrounding rural district (gmina) of the same name.
-
B.
Balvi
Balvi is a small town in eastern Latvia that serves as an important local administrative, cultural, and economic center in the Latgale region.
-
C.
Bogrod
Bogrod is a goblin banker who works at Gringotts Wizarding Bank in the Harry Potter series.
-
D.
Soligalich
Soligalich is a historic Russian town known for its preserved 18th–19th century architecture and location along the Kostroma River in Kostroma Oblast.
-
E.
Barysaw
Barysaw is a city in Belarus known as an important industrial and transportation center northeast of Minsk.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9646dfc908190bc398935d1d23537 |
completed | April 10, 2026, 8:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68eb388488190a30866e9a7a0bc41 |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 9, 2026, 5:26 p.m.