Triple
T25818537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mystery Series |
E650331
|
entity |
| Predicate | plotDrivenBy |
P86045
|
FINISHED |
| Object | Daisy |
—
|
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: Daisy | Statement: [The Mystery Series, plotDrivenBy, Daisy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotDrivenBy Context triple: [The Mystery Series, plotDrivenBy, Daisy]
-
A.
strategyDirectedBy
Indicates that the development, implementation, or oversight of a strategy is guided or controlled by a specified directing entity.
-
B.
isNarrativeDriven
chosen
Indicates that an entity’s primary structure or progression is guided by a storyline or plot rather than by mechanics, data, or other non-story elements.
-
C.
plotDetail
Indicates that one entity provides specific information or events that elaborate on the storyline of another entity.
-
D.
movementDirector
Indicates that one entity serves as the movement director (responsible for choreographing or directing movement) for another entity, such as a performance or production.
-
E.
directedIn
Indicates that one entity served as the director of another entity, such as a person directing a film, episode, or similar work.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600cb37f081908ad2ea805c555876 |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:27 a.m.