Triple
T15439892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medenine |
E369869
|
entity |
| Predicate | storageFunction |
P82748
|
FINISHED |
| Object | grain storage |
—
|
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: grain storage | Statement: [Medenine, storageFunction, grain storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageFunction Context triple: [Medenine, storageFunction, grain storage]
-
A.
hasStorageFunction
chosen
Indicates that an entity serves to store, retain, or hold another entity or resource for later use.
-
B.
storageLayer
Indicates a relationship where one entity functions as the storage layer or persistence tier used by another entity to store and retrieve data.
-
C.
storageOrgan
Indicates that one entity serves as a storage organ (a specialized structure for storing substances like nutrients or water) for another entity.
-
D.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
E.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03eddf258819082679970b7d2b6af |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.