Triple
T32900321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willem Dafoe as John Clark |
E841589
|
entity |
| Predicate | worksAlongsideInStory |
P72473
|
FINISHED |
| Object | Jack Ryan |
—
|
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: Jack Ryan | Statement: [Willem Dafoe as John Clark, worksAlongsideInStory, Jack Ryan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksAlongsideInStory Context triple: [Willem Dafoe as John Clark, worksAlongsideInStory, Jack Ryan]
-
A.
partnerInStory
Indicates that two or more entities are partners or collaborators within the context of a specific story or narrative.
-
B.
worksOnStoryAbout
Indicates that one entity is actively engaged in creating, developing, or contributing to a story whose subject or focus is another entity.
-
C.
associatedWithPersonInStory
Indicates that one entity has a connection or involvement with a specific person within the context of a story.
-
D.
playedAlongside
chosen
Indicates that two or more entities participated together at the same time in a shared activity, performance, or event.
-
E.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:19 a.m.