Triple
T29920847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie Albert as Capt. Erskine Cooney |
E759927
|
entity |
| Predicate | rankOfCharacter |
P152574
|
FINISHED |
| Object | Captain |
—
|
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: Captain | Statement: [Eddie Albert as Capt. Erskine Cooney, rankOfCharacter, Captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankOfCharacter Context triple: [Eddie Albert as Capt. Erskine Cooney, rankOfCharacter, Captain]
-
A.
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.
-
B.
rankingRole
Indicates that one entity holds a specific position or level in an ordered hierarchy or ranking relative to others.
-
C.
rankInBackstory
Indicates the position or status an entity holds within another entity’s narrative background or origin story.
-
D.
roleInRanking
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
E.
rankIn
chosen
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67793b72c8190ae654ae110b82d84 |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:14 p.m.