Triple
T35310728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blenheim, South Carolina |
E1019762
|
entity |
| Predicate | hasLocalBrand |
P40804
|
FINISHED |
| Object | Blenheim Ginger Ale |
—
|
NE NERFINISHED |
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: Blenheim Ginger Ale | Statement: [Blenheim, South Carolina, hasLocalBrand, Blenheim Ginger Ale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalBrand Context triple: [Blenheim, South Carolina, hasLocalBrand, Blenheim Ginger Ale]
-
A.
hasGlobalBrand
Indicates that an entity possesses a brand that is recognized and operates across multiple countries or worldwide.
-
B.
isBrand
Indicates that one entity functions as the commercial brand or label associated with another entity.
-
C.
hasCoBrand
Indicates that two brands are jointly associated or partnered in offering a product, service, or marketing initiative.
-
D.
hasCoreBrand
Indicates that one entity possesses, is associated with, or is defined by a primary or central brand.
-
E.
hasBrandName
chosen
Indicates that an entity is associated with or identified by a specific brand name.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:03 p.m.