Triple
T35180900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluebird |
E1015843
|
entity |
| Predicate | hasDirectorInNotableProduction |
P98246
|
FINISHED |
| Object | Simon Stephens |
—
|
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: Simon Stephens | Statement: [Bluebird, hasDirectorInNotableProduction, Simon Stephens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectorInNotableProduction Context triple: [Bluebird, hasDirectorInNotableProduction, Simon Stephens]
-
A.
notableDirector
Indicates that a person has directed a work (such as a film or show) in a way that is recognized as significant or distinguished.
-
B.
hasDirectorInKeyWork
Indicates that a director is associated with a key or primary work of an entity (such as a film, series, or major production).
-
C.
notableProductionDirector
chosen
Indicates that a person served as a significant or distinguished director for a particular production.
-
D.
hasNotableFilm
Indicates that an entity is associated with a film that is considered significant, well-known, or particularly noteworthy.
-
E.
workOfDirectorKnownFor
Indicates that a work (such as a film or show) is directed by a person for whom this work is one of their notable or best-known creations.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:02 p.m.