Triple
T206016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arista Records |
E4611
|
entity |
| Predicate | distributes |
P1951
|
FINISHED |
| Object | recordings |
—
|
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: recordings | Statement: [Arista Records, distributes, recordings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributes Context triple: [Arista Records, distributes, recordings]
-
A.
distribution
Indicates the act or pattern of giving, delivering, or spreading something from one source to multiple recipients or locations.
-
B.
distributor
chosen
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
-
C.
spreadBy
Indicates that something is transmitted, dispersed, or propagated through the agency or action of a specified entity or medium.
-
D.
distributionMethod
Indicates the means or channel through which something (such as a product, resource, or information) is delivered or made available to recipients.
-
E.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.