Triple
T24772893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Mirror: The National Anthem |
E619775
|
entity |
| Predicate | hasStandaloneStory |
P129131
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Black Mirror: The National Anthem, hasStandaloneStory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandaloneStory Context triple: [Black Mirror: The National Anthem, hasStandaloneStory, true]
-
A.
hasStandaloneTales
chosen
Indicates that an entity includes or is associated with independent, self-contained stories that can be understood without relying on a larger narrative.
-
B.
hasVariantStoriesIn
Indicates that an entity has alternative or differing narrative versions that occur or are found within a specified context or source.
-
C.
hasOriginalStory
Indicates that one entity serves as the original narrative source or story upon which the other entity is based or derived.
-
D.
hasSiblingInStory
Indicates that one character in a narrative has at least one sibling who also appears within the same story.
-
E.
hasStandaloneGame
Indicates that an entity has its own independently released, self-contained game associated with it.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 4:32 a.m.