Triple
T27070736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Fuzz (2007 film score) |
E685316
|
entity |
| Predicate | starringInRelatedWork |
P164488
|
FINISHED |
| Object | Simon Pegg |
—
|
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 Pegg | Statement: [Hot Fuzz (2007 film score), starringInRelatedWork, Simon Pegg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starringInRelatedWork Context triple: [Hot Fuzz (2007 film score), starringInRelatedWork, Simon Pegg]
-
A.
portrayedInWork
Indicates that an entity is depicted or represented as a character, figure, or subject within a specific creative work.
-
B.
associatedActOfCreator
Indicates a relationship where an act is linked to the creator responsible for or connected with that act.
-
C.
notableWorkFeaturing
Indicates that a particular notable work (such as a book, film, or artwork) prominently includes, showcases, or is centered around a given entity.
-
D.
appearsInWorkByTitle
Indicates that an entity appears in, is featured in, or is contained within a work identified by its title.
-
E.
appearsInWorkDirector
Indicates that an entity appears in a creative work in which the associated director is responsible for directing that work.
- F. None of above. chosen
Provenance (4 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 8:28 a.m.