Triple
T3564316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire Distribution |
E75407
|
entity |
| Predicate | businessScope |
P9642
|
FINISHED |
| Object | global music market |
—
|
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: global music market | Statement: [Empire Distribution, businessScope, global music market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessScope Context triple: [Empire Distribution, businessScope, global music market]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
businessFunction
chosen
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
C.
business
Indicates that an entity is engaged in commercial or professional activities, such as providing goods or services for profit.
-
D.
businessOrigin
Indicates the place, source, or context from which a business or commercial entity originates or was established.
-
E.
businessVenture
Indicates a relationship where entities jointly engage in, operate, or are involved with a commercial or entrepreneurial undertaking.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0a76c008190a2056b6d990776fe |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.