Triple
T10277798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troppau |
E241013
|
entity |
| Predicate | PolishName |
P15778
|
FINISHED |
| Object | Opawa |
E830699
|
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: Opawa | Statement: [Troppau, PolishName, Opawa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Opawa Context triple: [Troppau, PolishName, Opawa]
-
A.
Opawa
chosen
Opawa is the Polish name for the city of Opava, a historical urban center in the Czech Republic’s Silesian region.
-
B.
Wallerode
Wallerode is a village in the municipality of Amel in the German-speaking Community of eastern Belgium.
-
C.
Indian Pass
Indian Pass is a rugged mountain pass in New York’s Adirondack High Peaks region, known for its dramatic cliffs, remote wilderness character, and challenging hiking routes.
-
D.
Sanabad
Sanabad is the historical settlement that later developed into the modern Iranian city of Mashhad.
-
E.
Bivouac de la Fourche
Bivouac de la Fourche is a high-altitude alpine shelter in the Mont Blanc massif used as a base for challenging routes on the Brenva side.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d29f0cf08190a2c5e7523d5c731e |
completed | April 7, 2026, 9:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f8286b1881908b54037d1798f74a |
completed | April 9, 2026, 12:51 a.m. |
Created at: April 6, 2026, 11:37 a.m.