Triple
T36955957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enslaved: Odyssey to the West |
E914187
|
entity |
| Predicate | Andy SerkisRole |
P25662
|
FINISHED |
| Object | Monkey |
—
|
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: Monkey | Statement: [Enslaved: Odyssey to the West, Andy SerkisRole, Monkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Andy SerkisRole Context triple: [Enslaved: Odyssey to the West, Andy SerkisRole, Monkey]
-
A.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
B.
creditedRoleOf
Indicates that a particular role or position is formally acknowledged as being held or performed by a specific entity in a credit or attribution context.
-
C.
worksForCharacterPlayedBy
Indicates that one character is employed by, or works under, another character who is portrayed by a specific actor.
-
D.
has part in role
Indicates that an entity participates as a component or constituent specifically in a defined role within a larger whole or process.
-
E.
hasFictionalRole
chosen
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.