Triple
T3417126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallesches Tor |
E72035
|
entity |
| Predicate | hasInterchangeWith |
P1018
|
FINISHED |
| Object | U3 |
E91577
|
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: U3 | Statement: [Hallesches Tor, hasInterchangeWith, U3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U3 Context triple: [Hallesches Tor, hasInterchangeWith, U3]
-
A.
U3
chosen
U3 is one of the main lines of the Nuremberg U-Bahn rapid transit system in Nuremberg, Germany.
-
B.
U4
U4 is a line of the Frankfurt U-Bahn rapid transit system in Frankfurt, Germany.
-
C.
U5
U5 is one of the lines of the Frankfurt U-Bahn rapid transit system in Frankfurt, Germany.
-
D.
U1
U1 is a major line of the Nuremberg U-Bahn rapid transit system, connecting key districts across the Nuremberg metropolitan area.
-
E.
UP-32
UP-32 is the vehicle registration code assigned to motor vehicles registered in the city of Lucknow, Uttar Pradesh, India.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92c20fc81909b5debced20ec083 |
completed | March 8, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3546c88008190980a51195251af91 |
completed | March 13, 2026, 12:03 a.m. |
Created at: March 8, 2026, 3:15 p.m.