Triple
T28071668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flute sonatas, Op. 2 |
E709417
|
entity |
| Predicate | relatedWorkCreatorOccupation |
P200974
|
FINISHED |
| Object | violinist |
—
|
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: violinist | Statement: [Flute sonatas, Op. 2, relatedWorkCreatorOccupation, violinist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkCreatorOccupation Context triple: [Flute sonatas, Op. 2, relatedWorkCreatorOccupation, violinist]
-
A.
relatedWorkCreator
Indicates that the creator of one work is related (e.g., by authorship, contribution, or collaboration) to the creation of another work.
-
B.
coCreatorOccupation
Indicates that two or more co-creators share the same occupation or professional role in relation to a creation or project.
-
C.
creatorOccupation
Indicates the professional role or job that the creator of an entity holds or held.
-
D.
authorWorkCreator
Indicates that an entity is the creator (author) responsible for producing a particular work.
-
E.
fieldOfWorkOfCreator
Indicates the professional or thematic field in which a creator primarily works or produces their creations.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
| PDg | Predicate description generation | batch_69ffbf8402c48190a9bf3c3fcb874508 |
completed | May 9, 2026, 11:13 p.m. |
Created at: April 27, 2026, 8:46 p.m.