Triple
T14257383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oranienburger Tor |
E353419
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | OT |
E353419
|
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: OT | Statement: [Oranienburger Tor, hasAbbreviation, OT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OT Context triple: [Oranienburger Tor, hasAbbreviation, OT]
-
A.
OT
OT is the abbreviation for Organisation Todt, the Nazi-era civil and military engineering group responsible for large-scale construction projects such as the Atlantic Wall.
-
B.
OT
chosen
OT is the station code for Oranienburger Tor, a Berlin U-Bahn station on the city’s central U6 line.
-
C.
OT
OT is the commonly used abbreviation for the Teide Observatory, a major astronomical research facility located on Tenerife in Spain’s Canary Islands.
-
D.
OT
OT is the vehicle registration code used on license plates for vehicles registered in Olt County, Romania.
-
E.
OTT
OTT is the standard three-letter abbreviation used for the National Hockey League team, the Ottawa Senators.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6352611c819090d062fe3079cd03 |
completed | April 14, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd325f213881909acf776ff4831c30 |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:09 a.m.