Triple
T3652444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS |
E77449
|
entity |
| Predicate | appliesTo |
P1129
|
FINISHED |
| Object | City of Osnabrück |
E22113
|
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: City of Osnabrück | Statement: [OS, appliesTo, City of Osnabrück]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Osnabrück Context triple: [OS, appliesTo, City of Osnabrück]
-
A.
Osnabrück
chosen
Osnabrück is a historic city in Lower Saxony, Germany, known for its medieval architecture and role in the Peace of Westphalia.
-
B.
Münster
Münster is a historic city in western Germany known as one of the principal sites where the Peace of Westphalia treaties were negotiated and signed, ending the Thirty Years' War in 1648.
-
C.
Hildesheim
Hildesheim is a historic city in northern Germany renowned for its medieval architecture and UNESCO-listed Romanesque churches.
-
D.
Nienburg
Nienburg is a historic town in Lower Saxony, Germany, known for its medieval architecture and scenic location along the Weser River.
-
E.
Detmold
Detmold is a historic town in northwestern Germany that served as the capital and residence city of the former Principality of Lippe.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b664448190986b5223d59de282 |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44f435c088190976c1dab165665f1 |
completed | March 13, 2026, 5:54 p.m. |
Created at: March 8, 2026, 3:24 p.m.