Triple
T33776421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ally Sutton |
E865534
|
entity |
| Predicate | hasPrimaryStoryArcIn |
P196218
|
FINISHED |
| Object | Trust Me |
E246927
|
NE 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: Trust Me | Statement: [Ally Sutton, hasPrimaryStoryArcIn, Trust Me]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryStoryArcIn Context triple: [Ally Sutton, hasPrimaryStoryArcIn, Trust Me]
-
A.
hasNarrativeArcIn
chosen
Indicates that an entity’s storyline or narrative progression occurs within or is contained by a specified work, context, or medium.
-
B.
hasNarrativeArcOf
Indicates that one entity embodies, represents, or corresponds to the narrative arc (story progression or plot structure) of another entity.
-
C.
hasPrimaryStory
Indicates that one entity is designated as the main or most important story associated with another entity.
-
D.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
E.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
- F. None of above.
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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01cb89ff448190b60ee3d148ce76fc |
completed | May 11, 2026, 12:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3692c2b9748190a038d8684cdf2a63 |
completed | June 20, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_6a01ca7604b48190bb8643c17c3a8c85 |
completed | May 11, 2026, 12:24 p.m. |
Created at: May 1, 2026, 1:45 a.m.