Triple
T30357192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 173dB |
E772180
|
entity |
| Predicate | associatedWorkCatalogue |
P153201
|
FINISHED |
| Object | Köchel catalogue of Mozart’s works |
E1716911
|
NE 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: Köchel catalogue of Mozart’s works | Statement: [K. 173dB, associatedWorkCatalogue, Köchel catalogue of Mozart’s works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkCatalogue Context triple: [K. 173dB, associatedWorkCatalogue, Köchel catalogue of Mozart’s works]
-
A.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
B.
associatedWithWorkOf
Indicates that one entity has a connection or involvement with the work, creation, or output produced by another entity.
-
C.
workCatalogue
chosen
Indicates a relationship where a work is included in, documented by, or associated with a specific catalogue.
-
D.
associatedWorkType
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
E.
associatedWorkSection
Indicates that one work or resource is related to a specific section or part of another work.
- F. None of above.
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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2798a315248190ae4039e6310f8213 |
completed | June 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:57 p.m.