Triple
T1523507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-1 |
E32282
|
entity |
| Predicate | landingRunway |
P1654
|
FINISHED |
| Object | Runway 23 |
—
|
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 23 | Statement: [STS-1, landingRunway, Runway 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingRunway Context triple: [STS-1, landingRunway, Runway 23]
-
A.
landingMethod
Indicates the manner or technique by which something or someone arrives and comes to rest at a destination, typically from the air or space.
-
B.
runway
chosen
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
C.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
D.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
E.
runwayEnd
Indicates that one entity represents the end point or terminus of a runway associated with the other 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.