Triple
T37137608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accused (US TV series) |
E920011
|
entity |
| Predicate | storyToldFrom |
P187647
|
FINISHED |
| Object | defendant’s point of view |
—
|
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: defendant’s point of view | Statement: [Accused (US TV series), storyToldFrom, defendant’s point of view]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyToldFrom Context triple: [Accused (US TV series), storyToldFrom, defendant’s point of view]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
storyTime
Indicates that one entity is narrating or sharing a story with another entity, typically in a designated or scheduled period for storytelling.
-
C.
retellsStoryOf
Indicates that one entity recounts or narrates the story originally told or experienced by another entity.
-
D.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
E.
sourceOfStories
Indicates that one entity serves as the origin or provider of stories for another entity.
- F. None of above. chosen
Provenance (4 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.