Triple
T28717024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathfinder lander |
E729986
|
entity |
| Predicate | usedDescentSystem |
P64600
|
FINISHED |
| Object | parachute |
—
|
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: parachute | Statement: [Pathfinder lander, usedDescentSystem, parachute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDescentSystem Context triple: [Pathfinder lander, usedDescentSystem, parachute]
-
A.
descentSystem
Indicates the kinship or inheritance pattern through which lineage, membership, or rights are traced (e.g., matrilineal, patrilineal, or bilateral).
-
B.
descentStageUsedFor
chosen
Indicates that a particular descent stage is utilized to support or perform an associated mission, operation, or vehicle activity.
-
C.
descentType
Indicates the specific manner or category of downward movement or lineage relationship between entities.
-
D.
descentTarget
Indicates that an entity is the intended destination or endpoint toward which another entity is descending.
-
E.
hasDescent
Indicates that one entity is a descendant of another, typically through a lineage or ancestry 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:51 a.m.