Triple
T29147638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Double (2013 film) |
E738814
|
entity |
| Predicate | leadActorForCharacterJamesSimon |
P169669
|
FINISHED |
| Object | Jesse Eisenberg |
—
|
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: Jesse Eisenberg | Statement: [The Double (2013 film), leadActorForCharacterJamesSimon, Jesse Eisenberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadActorForCharacterJamesSimon Context triple: [The Double (2013 film), leadActorForCharacterJamesSimon, Jesse Eisenberg]
-
A.
leadActorForCharacterSimonJames
Indicates that a person is the primary actor portraying the character Simon James in a production.
-
B.
roleOfJames Windon
Indicates that the specified role or position is held by James Windon.
-
C.
leadActorForCharacter Philip Shayne
Indicates that the specified person is the primary actor portraying the character Philip Shayne.
-
D.
leadActorForCharacterLance
Indicates that the referenced person is the primary actor who portrays the character named Lance.
-
E.
leadActorForCharacterGeorge
Indicates that the specified person is the primary actor portraying the character George.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 28, 2026, 11:40 a.m.