Triple
T10194738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Pace |
E238131
|
entity |
| Predicate | playedByCharacter |
P1507
|
FINISHED |
| Object | Dominic Monaghan as Charlie Pace |
—
|
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: Dominic Monaghan as Charlie Pace | Statement: [Charlie Pace, playedByCharacter, Dominic Monaghan as Charlie Pace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedByCharacter Context triple: [Charlie Pace, playedByCharacter, Dominic Monaghan as Charlie Pace]
-
A.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
B.
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.
-
C.
portrayedByAlsoPlays
Indicates that the actor who portrays a given character also plays another specified role or character.
-
D.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
E.
characterInPlayBy
Indicates that a character appears in or is part of a play authored or created by a specific person.
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdedc7cc748190bceb8f657afcc054 |
completed | April 2, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:13 p.m.