Triple
T29805939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fish People |
E756839
|
entity |
| Predicate | rightsManagementScope |
P5018
|
FINISHED |
| Object | Kate Bush back catalog |
—
|
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: Kate Bush back catalog | Statement: [Fish People, rightsManagementScope, Kate Bush back catalog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightsManagementScope Context triple: [Fish People, rightsManagementScope, Kate Bush back catalog]
-
A.
rightsManagement
Indicates the management, control, and enforcement of usage rights or permissions associated with an entity or resource.
-
B.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
C.
licenseScope
Indicates the specific rights, limitations, and conditions that define how and where a license may be used or applied.
-
D.
scopeOfUse
chosen
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
E.
rightsRecognizedIn
Indicates that certain rights are formally acknowledged or upheld within a specified context, such as a legal system, jurisdiction, or document.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6752a26788190a157810a0a585268 |
completed | May 2, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:21 p.m.