Triple
T15463248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPG |
E371956
|
entity |
| Predicate | runwayOrientation_05_23 |
P6272
|
FINISHED |
| Object | roughly northeast–southwest |
—
|
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 northeast–southwest | Statement: [PPG, runwayOrientation_05_23, roughly northeast–southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayOrientation_05_23 Context triple: [PPG, runwayOrientation_05_23, roughly northeast–southwest]
-
A.
hasRightRunwayIn25Direction
Indicates that an entity (typically an airport or airfield) possesses a right-hand runway aligned or oriented in the 25 direction.
-
B.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
C.
runwayEndHeading
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
D.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
E.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1927708190a0d2b63e75469a0e |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.