Triple
T31917854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 15R/33L |
E814883
|
entity |
| Predicate | hasNumberOfParallelRunwaysAtAirport |
P2956
|
FINISHED |
| Object | 2 |
—
|
LITERAL 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: 2 | Statement: [Runway 15R/33L, hasNumberOfParallelRunwaysAtAirport, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfParallelRunwaysAtAirport Context triple: [Runway 15R/33L, hasNumberOfParallelRunwaysAtAirport, 2]
-
A.
numberOfRunways
chosen
Indicates the quantity of runways associated with a given entity, such as an airport or airfield.
-
B.
hasParallelRunway
Indicates that one runway is parallel in orientation and alignment to another runway.
-
C.
hasParallelRunwaySystemRole
Indicates that an entity holds a specific role or function within a parallel runway system.
-
D.
hasParallelRunwayIndicator
Indicates that one runway serves as a parallel counterpart or reference indicator for another runway within an airport or airfield.
-
E.
isSingleRunwayForAirport
Indicates that a runway is the only (single) runway serving a particular airport.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 12:02 a.m.