Triple
T1856799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technical University of Braunschweig |
E41720
|
entity |
| Predicate | memberOf |
P10
|
FINISHED |
| Object | TU9 |
E126174
|
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: TU9 | Statement: [Technical University of Braunschweig, memberOf, TU9]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TU9 Context triple: [Technical University of Braunschweig, memberOf, TU9]
-
A.
TU9
chosen
TU9 is an alliance of nine leading German Institutes of Technology focused on engineering and natural sciences research and education.
-
B.
TU
TU is the international vehicle registration code assigned to Tunisia.
-
C.
ZTU
ZTU is the IATA station code assigned to a specific passenger rail station in Miami, Florida, used for ticketing and travel logistics.
-
D.
the T
The T is the public transit system serving the Greater Boston area, operated by the Massachusetts Bay Transportation Authority.
-
E.
TNUA
TNUA is an academic association or network that includes Nagoya University among its member institutions.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb07fc5f08190a195a2f24d7b858a |
completed | March 7, 2026, 4:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69add1cb5b708190a0b89b157ea9da58 |
completed | March 8, 2026, 7:45 p.m. |
Created at: March 4, 2026, 7:33 p.m.