Triple
T28488016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Kay Live tour |
E720885
|
entity |
| Predicate | mainPerformerKnownFor |
P74889
|
FINISHED |
| Object | Phoenix Nights |
—
|
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: Phoenix Nights | Statement: [Peter Kay Live tour, mainPerformerKnownFor, Phoenix Nights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformerKnownFor Context triple: [Peter Kay Live tour, mainPerformerKnownFor, Phoenix Nights]
-
A.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
-
B.
actorKnownFor
Indicates that an actor is widely recognized or notable for a particular work, role, or contribution.
-
C.
performerNotableWork
chosen
Indicates that a performer is significantly associated with or best known for a particular work (such as a performance, production, or recording).
-
D.
laterKnownFor
Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
-
E.
creatorKnownFor
Indicates that a creator is especially recognized or notable for a particular work, contribution, or achievement.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 2:59 a.m.