Triple
T25193928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andre Anthony |
E630951
|
entity |
| Predicate | backstoryElementOf |
P35676
|
FINISHED |
| Object | Michonne |
—
|
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: Michonne | Statement: [Andre Anthony, backstoryElementOf, Michonne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backstoryElementOf Context triple: [Andre Anthony, backstoryElementOf, Michonne]
-
A.
expandsBackstoryOf
Indicates that one entity provides additional background details or context that elaborate on the history or origins of another entity.
-
B.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
C.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
D.
hasFictionalBackstory
Indicates that an entity is associated with an invented or imaginary narrative background rather than a real-world history.
-
E.
protagonistBackground
Indicates that one entity serves as the background, history, or prior circumstances of the protagonist entity in a narrative or story.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e1206f88190bfacdc420027c354 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:45 p.m.