Triple
T29358284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Edge of Extinction |
E744507
|
entity |
| Predicate | featuresTwist |
P90009
|
FINISHED |
| Object | Edge of Extinction |
—
|
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: Edge of Extinction | Statement: [Survivor: Edge of Extinction, featuresTwist, Edge of Extinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTwist Context triple: [Survivor: Edge of Extinction, featuresTwist, Edge of Extinction]
-
A.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
B.
twistType
Indicates the specific manner or category of twisting applied in a relationship or action between entities.
-
C.
featuresDemon
Indicates that an entity includes, depicts, or prominently involves a demon.
-
D.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
-
E.
hasTwist
chosen
Indicates that an entity (such as a story, object, or feature) includes an unexpected change, reversal, or surprising element relative to what was previously established or anticipated.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: April 28, 2026, 2:14 p.m.