Triple
T26727221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palapa B2 |
E673865
|
entity |
| Predicate | recoveryMission |
P151421
|
FINISHED |
| Object | STS-51A |
—
|
NE NERFINISHED |
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: STS-51A | Statement: [Palapa B2, recoveryMission, STS-51A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveryMission Context triple: [Palapa B2, recoveryMission, STS-51A]
-
A.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
B.
recoveryForce
Indicates the force exerted to restore an object or system from a displaced, deformed, or disturbed state back toward its original or equilibrium condition.
-
C.
rescueOperation
chosen
Indicates an action where one entity undertakes efforts to save or free another entity from danger, harm, or a threatening situation.
-
D.
designedToRecover
Indicates that something is intentionally created or configured for the purpose of regaining a prior state, condition, or resource after loss, damage, or failure.
-
E.
publicMission
Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:43 a.m.