Triple
T31347776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sprinkles |
E799496
|
entity |
| Predicate | isPutInFreezerBy |
P156995
|
FINISHED |
| Object | Dwight Schrute |
—
|
NE NERFINISHED |
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: Dwight Schrute | Statement: [Sprinkles, isPutInFreezerBy, Dwight Schrute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPutInFreezerBy Context triple: [Sprinkles, isPutInFreezerBy, Dwight Schrute]
-
A.
usesWeightFreezing
Indicates that an entity applies weight freezing, keeping certain model parameters fixed and untrainable during learning or optimization.
-
B.
isRefrigeratedForSale
Indicates that an item is kept under refrigeration specifically for the purpose of being offered for sale.
-
C.
frozenIn
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by another entity.
-
D.
refrigerated
chosen
Indicates that something is kept at a low temperature, typically in a refrigerator, to preserve its condition or freshness.
-
E.
refrigerationRequirement
Indicates that the related item or substance must be kept at a specified refrigerated temperature or storage condition.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f19a79c81909647d8eef6706e44 |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.