Triple
T9068647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISWC |
E217306
|
entity |
| Predicate | uniqueFor |
P9321
|
FINISHED |
| Object | each distinct musical work |
—
|
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: each distinct musical work | Statement: [ISWC, uniqueFor, each distinct musical work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniqueFor Context triple: [ISWC, uniqueFor, each distinct musical work]
-
A.
isUniqueTo
Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
-
B.
uniquenessCondition
Indicates that a specified element, value, or combination of attributes must be unique within a given set, context, or domain, with no duplicates allowed.
-
C.
typeOfUniqueness
Indicates that one entity’s uniqueness is characterized, classified, or constrained by the specific kind or mode of uniqueness associated with another entity.
-
D.
uniqueClaim
Indicates that a claim is distinct and not duplicated or shared with any other claim in the given context.
-
E.
isUniqueWithinStandard
chosen
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ba250819085fa49e0059d06c1 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.