Triple
T4170778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Best British Film |
E84555
|
entity |
| Predicate | genreOfWorksRecognized |
P38820
|
FINISHED |
| Object | all film genres |
—
|
LITERAL FINISHED |
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: all film genres | Statement: [Best British Film, genreOfWorksRecognized, all film genres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfWorksRecognized Context triple: [Best British Film, genreOfWorksRecognized, all film genres]
-
A.
genreOfWorkHonored
chosen
Indicates the specific genre or type of creative work for which an honor, award, or recognition is given.
-
B.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
C.
formatOfWorks
Indicates the specific medium, layout, or structural form in which works are created, presented, or published.
-
D.
recognizesWorkOf
Indicates that one entity acknowledges, identifies, or gives credit to the work or contributions produced by another entity.
-
E.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c87cc88190a9ec3712db18a8a7 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.