Triple
T14241713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piasts of Gniezno |
E353023
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Gniezno |
E226276
|
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: Gniezno | Statement: [Piasts of Gniezno, locatedIn, Gniezno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gniezno Context triple: [Piasts of Gniezno, locatedIn, Gniezno]
-
A.
Gniezno
chosen
Gniezno is a historic city in west-central Poland, renowned as the country’s first capital and an early center of Polish statehood and Christianity.
-
B.
Ogrodzieniec
Ogrodzieniec is a town in southern Poland best known for the ruins of its medieval castle in the Kraków-Częstochowa Upland.
-
C.
Lidzbark Warmiński
Lidzbark Warmiński is a historic town in northern Poland known for its well-preserved Gothic castle and role as a former seat of the Warmian bishops.
-
D.
Płock
Płock is a historic city in central Poland known for its medieval architecture and scenic location on the banks of the Vistula River.
-
E.
Wołomin
Wołomin is a town in east-central Poland that functions as a suburban community within the greater Warsaw metropolitan area.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6244ad188190b9d9db7914240410 |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd46794e9c819093312a2c304e554e |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:08 a.m.