Triple
T35778098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emser pastilles |
E1034352
|
entity |
| Predicate | shouldBeStoredIn |
P184100
|
FINISHED |
| Object | dry place |
—
|
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: dry place | Statement: [Emser pastilles, shouldBeStoredIn, dry place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shouldBeStoredIn Context triple: [Emser pastilles, shouldBeStoredIn, dry place]
-
A.
shouldBeStoredAt
chosen
Indicates that an entity is required or recommended to be kept or maintained at a specified location or storage condition.
-
B.
canBeStoredFor
Indicates that something is suitable or allowed to be kept in storage for a certain duration or under certain conditions.
-
C.
laterStoredIn
Indicates that an entity is subsequently placed or kept within a particular storage location or container at a later point in time.
-
D.
canBeStoredOn
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
-
E.
storedBy
Indicates that one entity is kept, maintained, or held in storage by another entity.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.