Triple
T1329446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masovian Voivodeship |
E28607
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Radom |
E168498
|
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: Radom | Statement: [Masovian Voivodeship, contains, Radom]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Radom Context triple: [Masovian Voivodeship, contains, Radom]
-
A.
Radom
chosen
Radom is a city in central Poland known as an important regional industrial and cultural center.
-
B.
Lublin
Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
-
C.
Łódź
Łódź is one of Poland’s largest cities, historically known as a major industrial and textile manufacturing center.
-
D.
Białystok
Białystok is a city in northeastern Poland best known as the birthplace of L. L. Zamenhof and the cradle of the international language Esperanto.
-
E.
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.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c30c948190afc6342b3dcda948 |
completed | March 1, 2026, 10:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afc00ddbf48190866fb79b4b4a2857 |
completed | March 10, 2026, 6:54 a.m. |
Created at: March 1, 2026, 7:55 p.m.