Triple
T7526215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 22 |
E177898
|
entity |
| Predicate | hasReciprocalEnd |
P6587
|
FINISHED |
| Object | Runway 04 |
—
|
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: Runway 04 | Statement: [Runway 22, hasReciprocalEnd, Runway 04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReciprocalEnd Context triple: [Runway 22, hasReciprocalEnd, Runway 04]
-
A.
hasReverse
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
-
B.
hasCounterpart
chosen
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
C.
hasInterchangesWith
Indicates that two transportation routes, lines, or services share one or more points where passengers can transfer between them.
-
D.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
E.
isInverseOf
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.