Triple
T32060785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fireplace |
E818740
|
entity |
| Predicate | partOfStoryArcOf |
P103369
|
FINISHED |
| Object | Ember Lumen |
—
|
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: Ember Lumen | Statement: [The Fireplace, partOfStoryArcOf, Ember Lumen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfStoryArcOf Context triple: [The Fireplace, partOfStoryArcOf, Ember Lumen]
-
A.
hasNarrativeArcOf
Indicates that one entity embodies, represents, or corresponds to the narrative arc (story progression or plot structure) of another entity.
-
B.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
C.
partOfPlot
chosen
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
D.
firstMajorStoryArc
Indicates that the related entity represents the initial or earliest major story arc associated with another narrative work or series.
-
E.
hasNarrativeArcIn
Indicates that an entity’s storyline or narrative progression occurs within or is contained by a specified work, context, or medium.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 1, 2026, 12:21 a.m.