Triple
T27924906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Britain |
E706304
|
entity |
| Predicate | hasRadioVersion |
P175641
|
FINISHED |
| Object | Little Britain (radio series) |
—
|
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: Little Britain (radio series) | Statement: [Little Britain, hasRadioVersion, Little Britain (radio series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadioVersion Context triple: [Little Britain, hasRadioVersion, Little Britain (radio series)]
-
A.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
B.
hasRadioPresence
Indicates that an entity maintains a detectable or active presence in radio broadcasts or radio communication channels.
-
C.
radioVersionType
Indicates the specific type or category of a radio version associated with an item or entity.
-
D.
radioVersionName
Indicates the specific name or label assigned to a version of a radio-related item or system.
-
E.
hasAlternativeRadioVersionWith
Indicates that one audio track has a corresponding alternative version specifically edited or mixed for radio play.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 27, 2026, 6:59 p.m.