Triple
T7574516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palapa B2 |
E179327
|
entity |
| Predicate | failureType |
P12733
|
FINISHED |
| Object | orbit insertion failure |
—
|
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: orbit insertion failure | Statement: [Palapa B2, failureType, orbit insertion failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failureType Context triple: [Palapa B2, failureType, orbit insertion failure]
-
A.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
missionFailure
chosen
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
D.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
E.
typeOfFaulting
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f948e1e08190ad807292365a0c27 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.