Triple
T14524355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trincomalee Airport |
E340733
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | TRR |
E340732
|
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: TRR | Statement: [Trincomalee Airport, hasIATACode, TRR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TRR Context triple: [Trincomalee Airport, hasIATACode, TRR]
-
A.
TRR
chosen
TRR is the IATA airport code for Trincomalee Airport in Sri Lanka.
-
B.
RTR
RTR is a Swiss public broadcasting division that produces and distributes radio, television, and online content in the Romansh language.
-
C.
RTR
RTR is the commonly used nickname for the Recruit Training Regiment, a military unit responsible for initial training of new recruits.
-
D.
TRE
TRE is the station code for the Trenton Transit Center, a major rail hub in Trenton, New Jersey serving Amtrak, NJ Transit, and SEPTA trains.
-
E.
TRE
TRE is the IATA airport code for Tiree Airport, which serves the island of Tiree in Scotland’s Inner Hebrides.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea04f16f88190ba357b0f8021b46b |
completed | April 14, 2026, 8:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a50324481909713bbf68295e839 |
completed | May 8, 2026, 5:53 a.m. |
Created at: April 10, 2026, 1:22 a.m.