Triple
T32900334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willem Dafoe as John Clark |
E841589
|
entity |
| Predicate | notablePerformanceForActor |
P74889
|
FINISHED |
| Object | Willem Dafoe |
E43748
|
NE 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: Willem Dafoe | Statement: [Willem Dafoe as John Clark, notablePerformanceForActor, Willem Dafoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePerformanceForActor Context triple: [Willem Dafoe as John Clark, notablePerformanceForActor, Willem Dafoe]
-
A.
notablePrimaryPerformance
Indicates that an entity is recognized for a primary or leading performance in a work or event.
-
B.
notablePerformanceYear
Indicates the year in which an entity delivered a particularly significant or distinguished performance.
-
C.
performerNotableWork
chosen
Indicates that a performer is significantly associated with or best known for a particular work (such as a performance, production, or recording).
-
D.
notableAdaptationPerformance
Indicates that an entity is recognized for a significant performance in an adaptation of another work.
-
E.
notableAppearanceIn
Indicates that an entity is prominently featured or plays a significant role in a particular work, event, or context.
- F. None of above.
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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34d258c74881908a496ac0b5f852fe |
completed | June 19, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:19 a.m.