Triple
T37774263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London College of Music |
E941640
|
entity |
| Predicate | examBoardFor |
P12353
|
FINISHED |
| Object | instrumental 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: instrumental music | Statement: [London College of Music, examBoardFor, instrumental music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examBoardFor Context triple: [London College of Music, examBoardFor, instrumental music]
-
A.
exam
Indicates that an entity administers, takes, or is associated with a formal test or assessment of knowledge, skills, or performance.
-
B.
examType
Indicates the specific category or format of an exam associated with an assessment or testing event.
-
C.
examProvider
chosen
Indicates that one entity is the organization or individual responsible for creating, administering, or supplying an exam to another entity.
-
D.
examSystem
Indicates a relationship where an entity functions as or belongs to an examination system, such as a framework or platform for creating, administering, or managing exams.
-
E.
workExamined
Indicates that one entity has examined, reviewed, or studied the work produced by another entity.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbaf20395c81909ad63b18b1007f1b |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.