Triple
T1206865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salon |
E25907
|
entity |
| Predicate | primaryDistributionChannel |
P10859
|
FINISHED |
| Object | internet |
—
|
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: internet | Statement: [Salon, primaryDistributionChannel, internet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDistributionChannel Context triple: [Salon, primaryDistributionChannel, internet]
-
A.
distributor
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
-
B.
primaryBroadcastMedium
chosen
Indicates the main communication channel or platform through which something (such as content, information, or a message) is originally transmitted or distributed.
-
C.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
D.
primaryExchange
Indicates the main or most significant transfer or trade interaction occurring between two parties or systems.
-
E.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc483b481908e5bfef5d2f4fc5a |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.