Triple
T33118449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorian |
E847522
|
entity |
| Predicate | productionStatusInStory |
P196295
|
FINISHED |
| Object | Discontinued model |
—
|
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: Discontinued model | Statement: [Dorian, productionStatusInStory, Discontinued model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionStatusInStory Context triple: [Dorian, productionStatusInStory, Discontinued model]
-
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.
storyCanonStatus
Indicates the canonical status of a story relative to an official or primary continuity.
-
D.
teamStatusInStory
Indicates the status or role a team holds within the context of a particular story or narrative.
-
E.
screenplayStatus
Indicates the current state or phase of a screenplay within its creation, revision, or production process.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69fe1fd58ad8819093d3d705e8521014 |
completed | May 8, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:27 a.m.