Triple
T7638814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolis GZM |
E172946
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Zbrosławice |
E848803
|
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: Zbrosławice | Statement: [Metropolis GZM, hasMember, Zbrosławice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zbrosławice Context triple: [Metropolis GZM, hasMember, Zbrosławice]
-
A.
Zbrosławice
chosen
Zbrosławice is a village in southern Poland known as the seat of its rural administrative district in the Silesian Voivodeship.
-
B.
Zbrzyca
Zbrzyca is a river in northern Poland that flows through the Pomeranian region before joining the Brda River.
-
C.
Brzesko
Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
-
D.
Bolesławiec
Bolesławiec is a historic town in southwestern Poland renowned for its traditional hand-decorated pottery.
-
E.
Zabierzów
Zabierzów is a village in southern Poland that serves as the administrative seat of its rural commune near the city of Kraków.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6facb14188190952de18fa2699784 |
completed | March 27, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e58a50d0748190a429af33cdced80a |
completed | April 20, 2026, 2:07 a.m. |
Created at: March 27, 2026, 3:57 p.m.