Triple
T8037235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway A 16L/34R |
E187137
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Runway A |
E187137
|
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: Runway A | Statement: [Runway A 16L/34R, alsoKnownAs, Runway A]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway A Context triple: [Runway A 16L/34R, alsoKnownAs, Runway A]
-
A.
Runway A
Runway A is a designated aircraft landing and takeoff strip located within North Field airport.
-
B.
Runway A 16L/34R
chosen
Runway A 16L/34R is one of the primary runways at Tokyo’s Haneda Airport, used for handling a high volume of domestic and international air traffic.
-
C.
Runway 4
Runway 4 is one end of a bidirectional airport runway, typically aligned toward a magnetic heading of approximately 040 degrees.
-
D.
Runway 5
Runway 5 is an airport runway designation indicating an approximate magnetic heading of 50 degrees, typically used when runway numbers are updated to reflect shifts in Earth’s magnetic variation.
-
E.
Runway 3R/21L
Runway 3R/21L is a primary paved runway at Tri-Cities Airport used for aircraft takeoffs and landings aligned roughly northeast–southwest.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f188e1c8190b92760c91d31f2df |
completed | March 31, 2026, 3:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc93bc11108190a34a35d0022f4bfd |
completed | April 1, 2026, 3:40 a.m. |
Created at: March 30, 2026, 5:22 p.m.