Triple
T36840833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRS for Music |
E910403
|
entity |
| Predicate | collectsFor |
P2196
|
FINISHED |
| Object | musical works |
—
|
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: musical works | Statement: [PRS for Music, collectsFor, musical works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsFor Context triple: [PRS for Music, collectsFor, musical works]
-
A.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
B.
collectedAs
Indicates that one entity has been gathered, acquired, or assembled as part of another entity, such as a collection, set, or group.
-
C.
collectionBy
Indicates that one entity is the collector or curator responsible for assembling, managing, or owning a particular collection of items represented by another entity.
-
D.
collects
chosen
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
E.
collectionCompiler
Indicates that an entity is responsible for compiling, assembling, or building a collection from its constituent elements or sources.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:13 p.m.