Triple
T18611691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cybertron |
E454907
|
entity |
| Predicate | statusInManyStories |
P83186
|
FINISHED |
| Object | war-torn |
—
|
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: war-torn | Statement: [Cybertron, statusInManyStories, war-torn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInManyStories Context triple: [Cybertron, statusInManyStories, war-torn]
-
A.
storyStatus
Indicates the current state or phase of a story within its lifecycle (e.g., planned, in progress, completed, or archived).
-
B.
narrativeStatus
Indicates the role or state of an element within a narrative, such as whether it is current, hypothetical, background, or otherwise positioned in the story’s progression.
-
C.
relationshipStatusInStory
Indicates the type or state of the relationship between entities as it exists within the context of a specific story or narrative.
-
D.
statusInManyContinuities
chosen
Indicates that an entity holds a particular status or role across multiple distinct continuities, timelines, or versions of a narrative or system.
-
E.
isStoried
Indicates that something has a rich history, reputation, or legacy built up over time, often marked by notable events or traditions.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d01ebd08190b6e646e3a749d7f5 |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.