Triple
T19586270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-51-B |
E490113
|
entity |
| Predicate | landingRunway |
P1654
|
FINISHED |
| Object | Runway 17 |
—
|
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 17 | Statement: [STS-51-B, landingRunway, Runway 17]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runway 17 Context triple: [STS-51-B, landingRunway, Runway 17]
-
A.
Runway 17
chosen
Runway 17 is a designated Space Shuttle landing runway used for the touchdown of NASA missions such as STS-26.
-
B.
Runway 14
Runway 14 is one of the designated landing and takeoff strips at Katherine Airport in Australia, serving regional air traffic operations.
-
C.
Runway 18
Runway 18 is the southern runway end of Runway 18/36, designated for aircraft approaches and departures on a heading of approximately 180 degrees.
-
D.
Runway 15
Runway 15 is a specific landing runway used for the touchdown of NASA’s Space Shuttle mission STS-121.
-
E.
Runway 11
Runway 11 is a performance and event venue located within the AsiaWorld-Expo complex in Hong Kong.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e640523d10819091320a61456f6437 |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.