Triple
T37911534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-Tinction Agenda |
E945699
|
entity |
| Predicate | precedesStoryline |
P132336
|
FINISHED |
| Object | X-Cutioner’s Song |
—
|
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: X-Cutioner’s Song | Statement: [X-Tinction Agenda, precedesStoryline, X-Cutioner’s Song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesStoryline Context triple: [X-Tinction Agenda, precedesStoryline, X-Cutioner’s Song]
-
A.
narrativeSequenceBefore
chosen
Indicates that one narrative event or element occurs earlier in the story’s sequence than another.
-
B.
precedesFeature
Indicates that one feature occurs, is implemented, or is introduced before another feature in a defined sequence or timeline.
-
C.
previousNarrator
Indicates that one entity served as the narrator immediately before another entity in a sequence of narrations.
-
D.
precedesInUniverse
Indicates that one event or entity occurs earlier than another within the timeline or causal order of a given fictional or conceptual universe.
-
E.
precedesInProgression
Indicates that one element occurs earlier than another within an ordered sequence or developmental progression.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 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. |
Created at: May 3, 2026, 4:20 p.m.