Triple
T17863424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shazad Latif as Ash Tyler |
E446129
|
entity |
| Predicate | rankInStory |
P110719
|
FINISHED |
| Object | Lieutenant |
—
|
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: Lieutenant | Statement: [Shazad Latif as Ash Tyler, rankInStory, Lieutenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInStory Context triple: [Shazad Latif as Ash Tyler, rankInStory, Lieutenant]
-
A.
rankWithinChapter
Indicates the relative ordering or position of an item among other items within the same chapter.
-
B.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
C.
protagonistRank
Indicates the relative narrative importance or centrality of a character within a story, typically ranking how primary they are as a protagonist compared to others.
-
D.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
E.
rankingRole
chosen
Indicates that one entity holds a specific position or level in an ordered hierarchy or ranking relative to others.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49791b0c08190b04a426bd274065d |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.