Triple
T1351617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fampyra |
E28893
|
entity |
| Predicate | storageCondition |
P8611
|
FINISHED |
| Object | store below 25°C |
—
|
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: store below 25°C | Statement: [Fampyra, storageCondition, store below 25°C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storageCondition Context triple: [Fampyra, storageCondition, store below 25°C]
-
A.
storageFacility
Indicates a relationship where one entity serves as a place or facility used to store another entity or its items.
-
B.
storageOption
chosen
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
C.
storageQuality
Indicates the degree or standard of how well something is stored, such as its preservation, safety, or suitability for use.
-
D.
stateOfPreservation
Indicates the condition or degree to which something has been maintained, conserved, or kept intact over time.
-
E.
storageRequirement
Indicates the amount or type of storage capacity or resources that an entity needs in order to function or be maintained.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26b1b4881908ae4b1b2c9b268a0 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.