Triple
T27384097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 34 |
E691317
|
entity |
| Predicate | isOppositeEndOf |
P147349
|
FINISHED |
| Object | Runway 16 |
—
|
NE NERFINISHED |
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: Runway 16 | Statement: [Runway 34, isOppositeEndOf, Runway 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOppositeEndOf Context triple: [Runway 34, isOppositeEndOf, Runway 16]
-
A.
hasOppositeDirectionTo
Indicates that one entity’s direction is exactly reversed or opposed to the direction of another entity.
-
B.
hasOppositeTerminus
chosen
Indicates that one terminus (end point) of an entity is directly opposite or facing the terminus of another entity.
-
C.
hasOppositeComponent
Indicates that one component is related to another as its opposite or contrasting counterpart within a system or structure.
-
D.
isExtremityOf
Indicates that one entity is an outermost part, boundary, or terminal point of another entity.
-
E.
hasOppositeStructure
Indicates that one entity possesses a structure that is the inverse or opposite in form, arrangement, or organization relative to another entity.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c89b7b88190a8b2af842f5f9cca |
completed | May 2, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:23 p.m.