Triple
T22872854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FNJ |
E567242
|
entity |
| Predicate | runwayOrientation_01_19 |
P6272
|
FINISHED |
| Object | roughly north–south |
—
|
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: roughly north–south | Statement: [FNJ, runwayOrientation_01_19, roughly north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayOrientation_01_19 Context triple: [FNJ, runwayOrientation_01_19, roughly north–south]
-
A.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
B.
runwayEndHeading
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
C.
runwayInformationAvailableIn
Indicates that information about a runway is available within or through a specified medium, source, or context.
-
D.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
E.
isPrimaryRunwayOf
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f55c4b88190adb49871e496ca54 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.