Triple
T21520916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debut Records |
E530971
|
entity |
| Predicate | businessCharacteristic |
P101071
|
FINISHED |
| Object | artist-run label |
—
|
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: artist-run label | Statement: [Debut Records, businessCharacteristic, artist-run label]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessCharacteristic Context triple: [Debut Records, businessCharacteristic, artist-run label]
-
A.
businessTrait
chosen
Indicates that an entity possesses a particular business-related characteristic, quality, or attribute in relation to another entity or context.
-
B.
domainCharacteristic
Indicates that a domain or area of interest possesses a particular characteristic or defining property.
-
C.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
E.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884bfa548190a39e5992ed6bb8a8 |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.