Triple
T33051987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | runway system of Osaka International Airport |
E845750
|
entity |
| Predicate | secondaryRunway |
P130266
|
FINISHED |
| Object | Runway 14L/32R |
—
|
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: Runway 14L/32R | Statement: [runway system of Osaka International Airport, secondaryRunway, Runway 14L/32R]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryRunway Context triple: [runway system of Osaka International Airport, secondaryRunway, Runway 14L/32R]
-
A.
hasSecondaryRunway
chosen
Indicates that an entity possesses an additional runway beyond its primary runway.
-
B.
isPrimaryRunwayOf
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
-
C.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
D.
hasParallelRunwaySystemRole
Indicates that an entity holds a specific role or function within a parallel runway system.
-
E.
hasSinglePrimaryRunway
Indicates that an airport or airfield possesses exactly one main runway used as its primary operational runway.
- F. None of above.
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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:24 a.m.