Triple
T36374171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shredded Wheat |
E895851
|
entity |
| Predicate | isOftenPackagedAs |
P90629
|
FINISHED |
| Object | individual biscuits in a box |
—
|
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: individual biscuits in a box | Statement: [Shredded Wheat, isOftenPackagedAs, individual biscuits in a box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenPackagedAs Context triple: [Shredded Wheat, isOftenPackagedAs, individual biscuits in a box]
-
A.
isPackagedFor
Indicates that one entity is prepared, contained, or wrapped specifically for use, sale, or distribution in connection with another entity.
-
B.
isPackaged
Indicates that one entity is enclosed, wrapped, or otherwise contained within another entity for storage, protection, or transport.
-
C.
isOftenImplementedAs
Indicates that one thing is frequently realized, instantiated, or carried out in the form of another.
-
D.
isFrequentlyIncludedIn
Indicates that something is regularly or commonly contained or made part of something else.
-
E.
typicalPackage
chosen
Indicates that something is the standard or commonly used package associated with a given entity or context.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:10 p.m.