Triple
T4256512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Drago |
E95986
|
entity |
| Predicate | roleInRockyIV |
P54992
|
FINISHED |
| Object | primary antagonist |
—
|
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: primary antagonist | Statement: [Ivan Drago, roleInRockyIV, primary antagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRockyIV Context triple: [Ivan Drago, roleInRockyIV, primary antagonist]
-
A.
roleOfWillChampion
Indicates that one entity is the specific role, position, or function held by Will Champion in relation to another entity.
-
B.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
C.
roleInMovement
Indicates the specific function, position, or contribution an entity has within a broader movement or collective effort.
-
D.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
E.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ec1971c81908f7a72418efa8bcc |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.