Triple
T10845609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intrepid |
E256000
|
entity |
| Predicate | descentStageStatus |
P64603
|
FINISHED |
| Object | remains on lunar surface |
—
|
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: remains on lunar surface | Statement: [Intrepid, descentStageStatus, remains on lunar surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descentStageStatus Context triple: [Intrepid, descentStageStatus, remains on lunar surface]
-
A.
descentStageUsedFor
Indicates that a particular descent stage is utilized to support or perform an associated mission, operation, or vehicle activity.
-
B.
descentStageFate
chosen
Indicates the outcome or final status of a descent stage after it has completed its descent-related function.
-
C.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
descentVia
Indicates a lineage relationship where one entity is descended from another through one or more intermediate generations or branches.
-
E.
descentFrom
Indicates that one entity is a descendant of another, typically through a lineage or ancestral relationship.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750d132e081909c977b3dc4110ca4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.