Triple
T22844978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YBTL |
E566188
|
entity |
| Predicate | hasIATAOverlap |
P55402
|
FINISHED |
| Object | TSV |
—
|
NE NERFINISHED |
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: TSV | Statement: [YBTL, hasIATAOverlap, TSV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TSV Context triple: [YBTL, hasIATAOverlap, TSV]
-
A.
TSV
chosen
TSV is the IATA airport code for Townsville Airport, a regional and military aviation hub in Townsville, Queensland, Australia.
-
B.
TSVWG
TSVWG is an IETF working group that develops and maintains standards and guidelines for transport-layer protocols and mechanisms on the Internet.
-
C.
TSV for Transport
TSV for Transport is the IETF area responsible for developing and maintaining transport-layer protocols and related technologies on the Internet.
-
D.
TSV Area
The TSV Area is the Internet Engineering Task Force (IETF) area responsible for transport-related protocols and technologies, such as congestion control and end-to-end data delivery.
-
E.
TSW
TSW is the station code for Stuttgart Schwabstraße, a key urban rail and S-Bahn station in Stuttgart, Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e882b148190985c085bb1a92aae |
completed | April 29, 2026, 3:44 a.m. |
Created at: April 17, 2026, 3:36 p.m.