Triple
T35067837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incendium |
E1011778
|
entity |
| Predicate | startsStoryArc |
P163477
|
FINISHED |
| Object | Finn and Flame Princess romance arc |
—
|
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: Finn and Flame Princess romance arc | Statement: [Incendium, startsStoryArc, Finn and Flame Princess romance arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsStoryArc Context triple: [Incendium, startsStoryArc, Finn and Flame Princess romance arc]
-
A.
storyArcStart
chosen
Indicates the point in a narrative where a particular story arc or plotline begins.
-
B.
narrativeStart
Indicates the point or event at which a narrative, story, or sequence of events begins.
-
C.
hasNarrativeArcOf
Indicates that one entity embodies, represents, or corresponds to the narrative arc (story progression or plot structure) of another entity.
-
D.
firstMajorStoryArc
Indicates that the related entity represents the initial or earliest major story arc associated with another narrative work or series.
-
E.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: May 3, 2026, 4:01 p.m.