Triple
T29216102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Follow |
E740670
|
entity |
| Predicate | hasMysteriousProtagonist |
P22515
|
FINISHED |
| Object | The Driver |
—
|
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: The Driver | Statement: [The Follow, hasMysteriousProtagonist, The Driver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMysteriousProtagonist Context triple: [The Follow, hasMysteriousProtagonist, The Driver]
-
A.
hasEnigmaticCharacter
chosen
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
-
B.
hasMystery
Indicates that one entity possesses, contains, or is associated with something unknown, secret, or unexplained in relation to another entity.
-
C.
hasMysteriousPast
Indicates that an entity possesses a past that is unknown, hidden, or only partially revealed, often implying secrets or unexplained events.
-
D.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
E.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 12:13 p.m.