Triple
T25664515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corn Ranch |
E643474
|
entity |
| Predicate | runwayFor |
P160918
|
FINISHED |
| Object | New Shepard crew capsule landing tests |
—
|
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: New Shepard crew capsule landing tests | Statement: [Corn Ranch, runwayFor, New Shepard crew capsule landing tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayFor Context triple: [Corn Ranch, runwayFor, New Shepard crew capsule landing tests]
-
A.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
B.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
C.
runwayUsedAs
chosen
Indicates that a particular runway is being utilized for a specific purpose, role, or operational function.
-
D.
runwayExtendedFor
Indicates that a runway has been lengthened or expanded to accommodate or serve a particular aircraft, operation, or purpose.
-
E.
usesRunwayOf
Indicates that one entity makes use of the runway that belongs to or is associated with 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 7 p.m.