Triple
T23740836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lazarus mission follow-up via Endurance |
E586665
|
entity |
| Predicate | backupPlan |
P41342
|
FINISHED |
| Object | Plan B colonization strategy |
—
|
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: Plan B colonization strategy | Statement: [Lazarus mission follow-up via Endurance, backupPlan, Plan B colonization strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupPlan Context triple: [Lazarus mission follow-up via Endurance, backupPlan, Plan B colonization strategy]
-
A.
supportsBackupPlans
Indicates that an entity provides assistance, resources, or endorsement for alternative or contingency plans associated with another entity or situation.
-
B.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
C.
recoveryPlan
chosen
Indicates a planned set of actions or strategies designed to restore a system, entity, or situation from a degraded, failed, or disrupted state back to an acceptable or normal condition.
-
D.
backupScope
Indicates the extent or range of data, resources, or components that are included in a backup operation.
-
E.
backupControlMode
Indicates that one entity serves as a fallback or secondary control mechanism for another when the primary control mode is unavailable or fails.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad61d908190a0a8493bbba95d49 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.