Triple
T12426807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Spartan |
E296918
|
entity |
| Predicate | laterStateOfBeing |
P13710
|
FINISHED |
| Object | revived from cryogenic freezing |
—
|
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: revived from cryogenic freezing | Statement: [John Spartan, laterStateOfBeing, revived from cryogenic freezing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterStateOfBeing Context triple: [John Spartan, laterStateOfBeing, revived from cryogenic freezing]
-
A.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
-
C.
laterDescribedAs
Indicates that an entity is referred to or characterized by a particular description or label at a later time.
-
D.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
E.
ultimateState
Indicates the final or end condition that an entity or process ultimately reaches after all preceding stages or transitions.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.