Triple
T27570764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbara Morgan |
E696026
|
entity |
| Predicate | wasBackupFor |
P50484
|
FINISHED |
| Object | Christa McAuliffe |
—
|
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: Christa McAuliffe | Statement: [Barbara Morgan, wasBackupFor, Christa McAuliffe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBackupFor Context triple: [Barbara Morgan, wasBackupFor, Christa McAuliffe]
-
A.
servesAsBackupFor
chosen
Indicates that one entity functions as a substitute or fallback that can take over the role or responsibilities of another entity if needed.
-
B.
backsUp
Indicates that one entity provides support, reinforcement, or confirmation for another entity’s actions, statements, or position.
-
C.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
D.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
E.
wasRestoredAt
Indicates that an entity was brought back to a previous or improved state at a specific time or place.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62febae708190bc3b9e4dab8c7698 |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:43 p.m.