Triple
T6847297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gravelly Point |
E157928
|
entity |
| Predicate | proximityToRunway |
P73489
|
FINISHED |
| Object | very close |
—
|
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: very close | Statement: [Gravelly Point, proximityToRunway, very close]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToRunway Context triple: [Gravelly Point, proximityToRunway, very close]
-
A.
hasRunwayApproachType
Indicates the specific type or category of approach procedure associated with a runway.
-
B.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
-
C.
isIntersectingRunwayWith
Indicates that one runway crosses or overlaps with another runway at some point along their lengths.
-
D.
runwayEnd
Indicates that one entity represents the end point or terminus of a runway associated with the other entity.
-
E.
runwayApproachOver
Indicates that an aircraft’s approach path to a runway passes over a particular object, area, or feature.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d7cd0e64819097c9c211df8bce54 |
completed | March 27, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d623aba88190a93ec9c83508c960 |
completed | March 27, 2026, 7:10 p.m. |
Created at: March 27, 2026, 2:20 p.m.