Triple
T11044079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 2 (Hamburg Airport) |
E261093
|
entity |
| Predicate | IATAAirportCodeOfParent |
P2569
|
FINISHED |
| Object | HAM |
E258716
|
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: HAM | Statement: [Terminal 2 (Hamburg Airport), IATAAirportCodeOfParent, HAM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HAM Context triple: [Terminal 2 (Hamburg Airport), IATAAirportCodeOfParent, HAM]
-
A.
HAM
HAM is the standard abbreviation used for the Canadian Football League team, the Hamilton Tiger-Cats.
-
B.
HAM
chosen
HAM is the IATA airport code for Hamburg Airport, the international airport serving the city of Hamburg, Germany.
-
C.
HAM
HAM is the standard abbreviation used for the Hamilton Bulldogs, a Canadian junior ice hockey team based in Hamilton, Ontario.
-
D.
Ham
Ham is a small town in the Somme department of northern France, known historically for its medieval fortress and strategic location.
-
E.
Ham
Ham is a suburban riverside district in southwest London, England, known for its historic houses, green spaces, and proximity to the River Thames.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7982e08548190aec04099cef9453c |
completed | April 9, 2026, 12:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a9f180688190ab2d1142b30a2836 |
completed | April 18, 2026, 3:57 p.m. |
Created at: April 8, 2026, 9:26 p.m.