Triple
T30999662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Hanks |
E789899
|
entity |
| Predicate | themePerformerCreditOftenParodied |
P171116
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tom Hanks, themePerformerCreditOftenParodied, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themePerformerCreditOftenParodied Context triple: [Tom Hanks, themePerformerCreditOftenParodied, yes]
-
A.
characterPerformer
Indicates that a performer portrays or voices a particular character in a work.
-
B.
originalHitPerformerParodied
Indicates that the subject is the original performer of a hit work that is being parodied by the object.
-
C.
associatedPerformerPersona
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
D.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
E.
hasFictionalPerformer
Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:56 p.m.