Triple
T12351901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmina Dąbie |
E294508
|
entity |
| Predicate | administrativeSeat |
P21613
|
FINISHED |
| Object | Dąbie |
E1005197
|
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: Dąbie | Statement: [Gmina Dąbie, administrativeSeat, Dąbie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dąbie Context triple: [Gmina Dąbie, administrativeSeat, Dąbie]
-
A.
Dąbie
Dąbie is a small town in central Poland, located in the Łódź Voivodeship along the Ner River.
-
B.
Dąbie
chosen
Dąbie is a settlement in Poland that serves as one of the localities within the administrative district of Gmina Dąbie.
-
C.
Trzciana
Trzciana is a village in southern Poland historically notable as the site of the 1629 Battle of Trzciana during the Polish–Swedish War.
-
D.
Byczyna
Byczyna is a historic small town in southwestern Poland known for its well-preserved medieval urban layout and defensive walls.
-
E.
Gubałówka
Gubałówka is a popular hill and tourist destination in the Polish Tatra region, known for its panoramic views of Zakopane and the surrounding mountains.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f8aa33c8190b22b7dff9559b8ed |
completed | April 10, 2026, 6:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b7e7454819099d89db93d0fc1ea |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 8, 2026, 9:53 p.m.