Triple
T27068106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donna and the Dynamos |
E685233
|
entity |
| Predicate | languageOfFictionalPerformances |
P52200
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Donna and the Dynamos, languageOfFictionalPerformances, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfFictionalPerformances Context triple: [Donna and the Dynamos, languageOfFictionalPerformances, English]
-
A.
languageOfFictionalUniverse
Indicates the language used or spoken within a fictional universe or setting.
-
B.
fictionalUniverseLanguage
Indicates that a language is used or exists within a particular fictional universe.
-
C.
areSpokenIn
Indicates that a particular language is used as a spoken means of communication within a specified region, community, or context.
-
D.
basedInFilmLanguage
Indicates that something is created, presented, or expressed using the language employed in a particular film.
-
E.
languageSpokenOnScreen
chosen
Indicates that a particular language is used in spoken dialogue or audible communication within an on-screen work (such as a film, show, or video).
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 27, 2026, 8:26 a.m.