Triple
T32058643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Pierce |
E818686
|
entity |
| Predicate | portrayedByInAvengersEndgame |
P1507
|
FINISHED |
| Object | Robert Redford |
—
|
NE NERFINISHED |
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: Robert Redford | Statement: [Alexander Pierce, portrayedByInAvengersEndgame, Robert Redford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedByInAvengersEndgame Context triple: [Alexander Pierce, portrayedByInAvengersEndgame, Robert Redford]
-
A.
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.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
portrayedByAlsoKnownFor
Indicates that an entity is portrayed by a person who is also notably known for another specific role or work.
-
D.
characterVoicedByTomHolland
Indicates that the character is voiced by Tom Holland.
-
E.
portrayedByInSequel
Indicates that an entity is portrayed by a particular actor or performer specifically in a sequel work (e.g., a sequel film, series, or game).
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 1, 2026, 12:21 a.m.