Triple
T12717279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitchell and Webb Live |
E303880
|
entity |
| Predicate | featuresWorkStyle |
P25796
|
FINISHED |
| Object | television-derived material |
—
|
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: television-derived material | Statement: [Mitchell and Webb Live, featuresWorkStyle, television-derived material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresWorkStyle Context triple: [Mitchell and Webb Live, featuresWorkStyle, television-derived material]
-
A.
hasWorkStyle
Indicates the type or manner in which an entity typically performs work or carries out tasks.
-
B.
workBehavior
Indicates how an entity typically acts, performs, or conducts itself in a work or professional context.
-
C.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
-
D.
workMode
Indicates the manner, configuration, or operational state in which an entity performs its work or function.
-
E.
featuresStyle
chosen
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9620bd6148190a2f50067a4c18c14 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.