Triple
T17093170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ervebo |
E414773
|
entity |
| Predicate | hasStorageRequirement |
P24102
|
FINISHED |
| Object | frozen 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: frozen storage | Statement: [Ervebo, hasStorageRequirement, frozen storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorageRequirement Context triple: [Ervebo, hasStorageRequirement, frozen storage]
-
A.
hasStorage
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
B.
storageRequirement
chosen
Indicates the amount or type of storage capacity or resources that an entity needs in order to function or be maintained.
-
C.
hasStorageClass
Indicates that one entity is assigned or associated with a particular storage class that defines how its data is stored or managed.
-
D.
hasEntryRequirement
Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
-
E.
hasStorageFunction
Indicates that an entity serves to store, retain, or hold another entity or resource for later use.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfabf548190a0d37bab3d4ef2fa |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.