Triple
T19295984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snyder’s of Hanover Pretzel Pieces |
E482562
|
entity |
| Predicate | portionForm |
P135168
|
FINISHED |
| Object | irregular pieces |
—
|
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: irregular pieces | Statement: [Snyder’s of Hanover Pretzel Pieces, portionForm, irregular pieces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portionForm Context triple: [Snyder’s of Hanover Pretzel Pieces, portionForm, irregular pieces]
-
A.
divisionFormat
Indicates the specific structural or organizational format in which a division or subdivision is arranged or presented.
-
B.
hasProportion
Indicates that one entity stands in a specified ratio, fraction, or relative share to another entity or whole.
-
C.
parallelDivision
Indicates that one entity is divided or partitioned in a way that runs parallel to the division or partitioning of another entity.
-
D.
divisionRepresentation
Indicates a relationship where one entity serves as a symbolic, visual, or structural representation of a division or partition of another entity.
-
E.
divisionIncluded
Indicates that one division is contained within or forms a part of another division.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8533c08190822a917ffa32812d |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:31 p.m.