Triple
T2736344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starship Human Landing System |
E60638
|
entity |
| Predicate | landingEnvironment |
P853
|
FINISHED |
| Object | airless body |
—
|
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: airless body | Statement: [Starship Human Landing System, landingEnvironment, airless body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingEnvironment Context triple: [Starship Human Landing System, landingEnvironment, airless body]
-
A.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
B.
landingArea
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
-
C.
landing
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
D.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
E.
landingRegion
Indicates the area or zone where an object or entity comes to rest or makes contact after moving or descending.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb11c66c81909058f2978aa5fae9 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.