Triple
T26760921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peace Arch Entertainment |
E674797
|
entity |
| Predicate | notableGenreWork |
P4
|
FINISHED |
| Object | The Tudors |
—
|
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: The Tudors | Statement: [Peace Arch Entertainment, notableGenreWork, The Tudors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGenreWork Context triple: [Peace Arch Entertainment, notableGenreWork, The Tudors]
-
A.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
B.
seriesGenreOfNotableWork
Indicates that a particular genre characterizes the notable work associated with a series.
-
C.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
-
D.
notableWork
chosen
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
E.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: April 27, 2026, 3:58 a.m.