Triple
T29657174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chips Ahoy! |
E750300
|
entity |
| Predicate | isWidelyAvailableIn |
P154561
|
FINISHED |
| Object | supermarkets |
—
|
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: supermarkets | Statement: [Chips Ahoy!, isWidelyAvailableIn, supermarkets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyAvailableIn Context triple: [Chips Ahoy!, isWidelyAvailableIn, supermarkets]
-
A.
isWidelyUsed
Indicates that something is commonly or extensively utilized across many contexts, users, or situations.
-
B.
mayBeAvailableIn
chosen
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
-
C.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
D.
isGenericAvailable
Indicates that a non-brand (generic) version of a product, typically a medication, is available as an alternative.
-
E.
isWidelyPerformed
Indicates that an action or behavior is carried out by a large number of individuals or groups across many contexts or locations.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f2850288190a394272ae49084e3 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:56 p.m.