Triple
T32348857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Granaries of Meknes |
E826537
|
entity |
| Predicate | designedToStore |
P154879
|
FINISHED |
| Object | grain |
—
|
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 | Statement: [Royal Granaries of Meknes, designedToStore, grain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToStore Context triple: [Royal Granaries of Meknes, designedToStore, grain]
-
A.
canBeStoredOn
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
-
B.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
C.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
D.
storedBy
Indicates that one entity is kept, maintained, or held in storage by another entity.
-
E.
designedToAccommodate
chosen
Indicates that something has been intentionally created or configured in a way that can suitably hold, support, or serve a particular thing, group, or purpose.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 1, 2026, 12:49 a.m.