Triple
T19691728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V8 Low Sodium |
E472849
|
entity |
| Predicate | hasShelfType |
P136942
|
FINISHED |
| Object | shelf-stable |
—
|
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: shelf-stable | Statement: [V8 Low Sodium, hasShelfType, shelf-stable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShelfType Context triple: [V8 Low Sodium, hasShelfType, shelf-stable]
-
A.
hasShelfmarkSystem
Indicates that an entity uses or is associated with a particular system or scheme for assigning shelfmarks or call numbers.
-
B.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasBenchType
Indicates that an entity is associated with or characterized by a specific type or category of bench.
-
E.
shelfMark
Indicates the classification or call number assigned to an item to specify its exact location on a shelf or within a storage system.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64210cddc8190836faa2996a44457 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.