Triple
T15672877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Bunny |
E377359
|
entity |
| Predicate | typicalStorage |
P119704
|
FINISHED |
| Object | freezer |
—
|
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: freezer | Statement: [Blue Bunny, typicalStorage, freezer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStorage Context triple: [Blue Bunny, typicalStorage, freezer]
-
A.
storageOrgan
Indicates that one entity serves as a storage organ (a specialized structure for storing substances like nutrients or water) for another entity.
-
B.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
C.
storageProperty
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
-
D.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
E.
canBeStoredOn
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f13b1b08190beabc9f4098aa096 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:16 a.m.