Triple
T22516891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strongbow Rosé |
E556670
|
entity |
| Predicate | hasTargetConsumers |
P14889
|
FINISHED |
| Object | cider drinkers |
—
|
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: cider drinkers | Statement: [Strongbow Rosé, hasTargetConsumers, cider drinkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetConsumers Context triple: [Strongbow Rosé, hasTargetConsumers, cider drinkers]
-
A.
hasNotableConsumerBase
Indicates that an entity is recognized for having a significant or prominent group of consumers or users.
-
B.
hasTarget
chosen
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
C.
hasTargetVisitors
Indicates that something is intended or designed to be visited by a specific group of people as its primary audience or users.
-
D.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
E.
hasProducer
Indicates that one entity serves as the producer or creator responsible for making or manufacturing another entity.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2df59c81909c4ae2f20f1cbb32 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.