Triple
T25530535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orwig Music Library |
E639897
|
entity |
| Predicate | hasSubjectSpecialist |
P39849
|
FINISHED |
| Object | music librarian |
—
|
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 librarian | Statement: [Orwig Music Library, hasSubjectSpecialist, music librarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectSpecialist Context triple: [Orwig Music Library, hasSubjectSpecialist, music librarian]
-
A.
hasSpecialist
chosen
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
B.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
C.
hasSpecialistStatus
Indicates that an entity holds a recognized specialist designation or status in a particular field, role, or context.
-
D.
subjectSpecialization
Indicates that one subject focuses on, or has expertise in, a particular field, topic, or area of knowledge.
-
E.
isConsideredSpecialtyOf
Indicates that one field, practice, or area of expertise is regarded as a specialized branch or subset of another broader field.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 3:14 p.m.