Triple
T34580487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kate McKay |
E887881
|
entity |
| Predicate | presentInWorkWithDirector |
P119719
|
FINISHED |
| Object | James Mangold |
—
|
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: James Mangold | Statement: [Kate McKay, presentInWorkWithDirector, James Mangold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentInWorkWithDirector Context triple: [Kate McKay, presentInWorkWithDirector, James Mangold]
-
A.
workedWithDirector
Indicates that one entity has collaborated professionally with a director on a project or production.
-
B.
precededByCollaborationWithDirector
Indicates that an event or work occurred after, and was directly preceded by, a collaboration with a specified director.
-
C.
basedOnWorkDirector
Indicates that one entity serves as the director of a work on which another entity is based.
-
D.
appearsInWorkDirector
chosen
Indicates that an entity appears in a creative work in which the associated director is responsible for directing that work.
-
E.
coPresentedWithWorkBy
Indicates that a work is presented together with another specified work, typically within the same event, session, or exhibition.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 2:03 a.m.