Triple
T13750447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke |
E330335
|
entity |
| Predicate | portrayedByInWork |
P1507
|
FINISHED |
| Object | Channing Tatum in G.I. Joe: Retaliation |
—
|
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: Channing Tatum in G.I. Joe: Retaliation | Statement: [Duke, portrayedByInWork, Channing Tatum in G.I. Joe: Retaliation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedByInWork Context triple: [Duke, portrayedByInWork, Channing Tatum in G.I. Joe: Retaliation]
-
A.
portrayedByWork
Indicates that a work (such as a film, book, or artwork) depicts, represents, or portrays a particular entity.
-
B.
portrayedInWork
Indicates that an entity is depicted or represented as a character, figure, or subject within a specific creative work.
-
C.
portrayedBy
chosen
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
D.
portrayedByAlsoPlays
Indicates that the actor who portrays a given character also plays another specified role or character.
-
E.
alsoPortrayedBy
Indicates that the same role or character is portrayed by an additional, different performer or actor.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02148c208190a882927905a861a6 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:08 p.m.