Triple
T30105826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retroactive series |
E765127
|
entity |
| Predicate | storyWorldRule |
P173274
|
FINISHED |
| Object | changes to the past create new consequences |
—
|
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: changes to the past create new consequences | Statement: [Retroactive series, storyWorldRule, changes to the past create new consequences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyWorldRule Context triple: [Retroactive series, storyWorldRule, changes to the past create new consequences]
-
A.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
B.
worldType
Indicates the classification or category of world or environment that an entity is associated with.
-
C.
worldbuildingFunction
Indicates the role or purpose something serves in constructing, shaping, or enriching an imagined world or setting.
-
D.
realmRuled
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
-
E.
worldName
Indicates that an entity has or is associated with a specific world’s name.
- F. None of above. chosen
Provenance (4 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 29, 2026, 7:09 p.m.