Triple
T8271653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | medronho brandy |
E193441
|
entity |
| Predicate | storageContainer |
P3676
|
FINISHED |
| Object | glass bottle |
—
|
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: glass bottle | Statement: [medronho brandy, storageContainer, glass bottle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageContainer Context triple: [medronho brandy, storageContainer, glass bottle]
-
A.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
B.
storageInterface
Indicates that one entity serves as a storage interface used by or associated with another entity for storing or retrieving data.
-
C.
storageFacility
chosen
Indicates a relationship where one entity serves as a place or facility used to store another entity or its items.
-
D.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
E.
storageLayer
Indicates a relationship where one entity functions as the storage layer or persistence tier used by another entity to store and retrieve data.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7986f8cc8190a529dda980dd6e98 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:50 p.m.