Triple
T32065374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 3R/21L |
E818863
|
entity |
| Predicate | alignedApproximately |
P173178
|
FINISHED |
| Object | 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: northeast–southwest | Statement: [Runway 3R/21L, alignedApproximately, northeast–southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignedApproximately Context triple: [Runway 3R/21L, alignedApproximately, northeast–southwest]
-
A.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
B.
representsApproximately
Indicates that one entity serves as an inexact or close-but-not-exact representation or value of another entity.
-
C.
approximationClass
Indicates a relationship where one entity is classified as an approximation or approximate representation of another.
-
D.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
E.
containsApproximately
Indicates that one entity holds or includes another entity in a quantity or proportion that is close to, but not exactly, a specified amount.
- F. None of above. chosen
Provenance (4 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b51cc924819080cd8f31a84f4b44 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:22 a.m.