Triple
T34907817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCM |
E1006777
|
entity |
| Predicate | hasProgramIn |
P204162
|
FINISHED |
| Object | music |
—
|
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: music | Statement: [CCM, hasProgramIn, music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgramIn Context triple: [CCM, hasProgramIn, music]
-
A.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
-
B.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
C.
isProgrammedIn
Indicates that a software system, application, or component is implemented using a particular programming language.
-
D.
hasHomeProgram
Indicates that an entity is associated with or belongs to a primary or designated home program.
-
E.
hasGlobalProgramme
Indicates that an entity operates, participates in, or is associated with a programme that is implemented or recognized at a global or international level.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a033d975d788190aafc4be10d6c5c1c |
completed | May 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_6a033cc2668481908cb696e57632a68f |
completed | May 12, 2026, 2:44 p.m. |
| PDg | Predicate description generation | batch_6a033d9690e081909f65653b0dc80e20 |
completed | May 12, 2026, 2:47 p.m. |
Created at: May 3, 2026, 4 p.m.