Triple
T25641971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corn Ranch, West Texas |
E642859
|
entity |
| Predicate | hasLandingZone |
P140135
|
FINISHED |
| Object | New Shepard booster landing area |
—
|
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 booster landing area | Statement: [Corn Ranch, West Texas, hasLandingZone, New Shepard booster landing area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandingZone Context triple: [Corn Ranch, West Texas, hasLandingZone, New Shepard booster landing area]
-
A.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
-
B.
hasIslandLanding
Indicates that an entity includes or provides a designated landing area or facility located on an island.
-
C.
hasLandingSystem
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
-
D.
hasLandingFacilities
chosen
Indicates that a location or structure is equipped with facilities that allow aircraft or other vehicles to land there.
-
E.
hasLandings
Indicates that an entity has one or more associated landing events or landing locations.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 21, 2026, 5:44 p.m.