Triple
T2073766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 12L/30R |
E44874
|
entity |
| Predicate | hasICAOAirportCode |
P419
|
FINISHED |
| Object | KSJC |
E44337
|
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: KSJC | Statement: [Runway 12L/30R, hasICAOAirportCode, KSJC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KSJC Context triple: [Runway 12L/30R, hasICAOAirportCode, KSJC]
-
A.
KSJC
chosen
KSJC is the ICAO airport code for Norman Y. Mineta San Jose International Airport, a major commercial airport serving San Jose and California’s Silicon Valley.
-
B.
KSOC
KSOC is the acronym for the Korean Sport & Olympic Committee, the national body responsible for overseeing Olympic and elite sports in South Korea.
-
C.
KS
KS is the standard two-letter postal abbreviation for the U.S. state of Kansas.
-
D.
KSLC
KSLC is the ICAO airport code for Salt Lake City International Airport, a major air transportation hub serving Salt Lake City, Utah.
-
E.
KTYS
KTYS is the ICAO airport code for McGhee Tyson Airport, the primary commercial airport serving Knoxville, Tennessee.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba101c008190840763d2f28fa8d7 |
completed | March 7, 2026, 5:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae30547b288190ab9466686f749768 |
completed | March 9, 2026, 2:28 a.m. |
Created at: March 4, 2026, 7:41 p.m.