Triple
T22918851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SunChips |
E568801
|
entity |
| Predicate | hasServingForm |
P150251
|
FINISHED |
| Object | bagged 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: bagged chips | Statement: [SunChips, hasServingForm, bagged chips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServingForm Context triple: [SunChips, hasServingForm, bagged chips]
-
A.
hasServingUse
Indicates that something is used or intended to be used for serving (e.g., food, drink, or portions).
-
B.
canServeIn
Indicates that one entity is eligible, authorized, or suitable to perform a role, function, or duty within another entity, context, or organization.
-
C.
served
Indicates that one entity provided a service, assistance, or role-based function to or for another entity.
-
D.
hasPositiveForm
Indicates that one form, variant, or expression is the positive (non-comparative, non-superlative, or affirmative) version of another.
-
E.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:42 p.m.