Triple
T22918857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SunChips |
E568801
|
entity |
| Predicate | isOftenPositionedNear |
P115314
|
FINISHED |
| Object | potato chips |
—
|
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: potato chips | Statement: [SunChips, isOftenPositionedNear, potato chips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenPositionedNear Context triple: [SunChips, isOftenPositionedNear, potato chips]
-
A.
positionOften
Indicates that one entity frequently holds, occupies, or is located at a particular position relative to another entity or context.
-
B.
occursNear
Indicates that one event or entity takes place or exists in close spatial proximity to another.
-
C.
suggestsFrequencyNear
Indicates that one entity proposes or implies an approximate or nearby frequency value relative to another entity.
-
D.
ensuredPositionNear
Indicates that one entity caused or guaranteed that another entity was located in close spatial proximity to a specified reference entity or point.
-
E.
oftenLocatedNear
chosen
Indicates that one entity is frequently found in close physical proximity to 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d316188190901d9356c07110e3 |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.