Triple
T36235476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrods Beauty |
E891365
|
entity |
| Predicate | availableChannel |
P71475
|
FINISHED |
| Object | in-store |
—
|
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: in-store | Statement: [Harrods Beauty, availableChannel, in-store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableChannel Context triple: [Harrods Beauty, availableChannel, in-store]
-
A.
availabilityChannel
chosen
Indicates the medium or channel through which something (such as a product, service, or resource) is made available or can be accessed.
-
B.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
C.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
D.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
E.
hasChannel
Indicates that one entity possesses, provides, or is associated with a particular communication or distribution channel.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.