Triple
T28238015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Hurlbut |
E711932
|
entity |
| Predicate | wroteForStudio |
P87665
|
FINISHED |
| Object | Universal Pictures |
—
|
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: Universal Pictures | Statement: [William Hurlbut, wroteForStudio, Universal Pictures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteForStudio Context triple: [William Hurlbut, wroteForStudio, Universal Pictures]
-
A.
producedForStudio
Indicates that a work (such as a film, show, or recording) was created under contract for, and on behalf of, a particular studio.
-
B.
collaboratedWithStudio
Indicates that an entity worked together with a studio on a shared project or production.
-
C.
workWrittenFor
Indicates that a creative work was specifically composed, produced, or created for a particular person, group, event, purpose, or medium.
-
D.
screenwriterForStudio
chosen
Indicates that a person serves as a screenwriter employed by or writing for a particular studio.
-
E.
wroteScreenplaysFor
Indicates that one entity is the author or writer of screenplays created for another entity, such as a film, series, or production.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 10:56 p.m.