Triple
T29791366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compass Point Studios |
E756413
|
entity |
| Predicate | usedByLabel |
P180797
|
FINISHED |
| Object | Island Records artists |
—
|
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: Island Records artists | Statement: [Compass Point Studios, usedByLabel, Island Records artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByLabel Context triple: [Compass Point Studios, usedByLabel, Island Records artists]
-
A.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
B.
usedLabel
Indicates that one entity has applied, assigned, or referenced a particular label to another entity or resource.
-
C.
usedInLabeling
Indicates that something is employed or applied as part of a labeling process or activity.
-
D.
usedByLine
Indicates that something (such as a resource, tool, or component) is utilized or operated by a particular line (for example, a production line, transit line, or code line).
-
E.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 29, 2026, 5:12 p.m.