Triple
T27936804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cool Mikado |
E700634
|
entity |
| Predicate | hasSourceMaterialComposer |
P46735
|
FINISHED |
| Object | Arthur Sullivan |
—
|
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: Arthur Sullivan | Statement: [The Cool Mikado, hasSourceMaterialComposer, Arthur Sullivan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceMaterialComposer Context triple: [The Cool Mikado, hasSourceMaterialComposer, Arthur Sullivan]
-
A.
hasSourceMaterial
chosen
Indicates that something is derived from, based on, or created using a particular source material.
-
B.
hasCoComposer
Indicates that an entity shares authorship of a musical composition with one or more other composers.
-
C.
hasSourceMaterialGenre
Indicates that the genre of the source material from which something is derived is specified.
-
D.
hasKnownComposer
Indicates that the work is associated with a composer whose identity is known and specified.
-
E.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 7:13 p.m.