Triple
T36572839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLV |
E902163
|
entity |
| Predicate | firstFlightOrbitInsertion |
P204939
|
FINISHED |
| Object | Failed to reach orbit |
—
|
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: Failed to reach orbit | Statement: [SLV, firstFlightOrbitInsertion, Failed to reach orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightOrbitInsertion Context triple: [SLV, firstFlightOrbitInsertion, Failed to reach orbit]
-
A.
MarsOrbitInsertion
Indicates the event or process of a spacecraft transitioning into a stable orbit around Mars.
-
B.
orbitInsertionDate
Indicates the date on which an object is placed into its designated orbit.
-
C.
firstUseInOrbit
Indicates that this is the first time the object or system is being used while in orbit.
-
D.
designedForOrbitInsertion
Indicates that something is intended or configured to perform or facilitate the insertion of an object into orbit.
-
E.
firstOrbitalMission
Indicates that the subject entity carried out or was involved in the earliest orbital spaceflight mission associated with the object entity.
- F. None of above. chosen
Provenance (4 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.