Triple
T5782623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryan Mound storage site |
E128194
|
entity |
| Predicate | usesStorageType |
P8611
|
FINISHED |
| Object | underground salt caverns |
—
|
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: underground salt caverns | Statement: [Bryan Mound storage site, usesStorageType, underground salt caverns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStorageType Context triple: [Bryan Mound storage site, usesStorageType, underground salt caverns]
-
A.
storeType
Indicates the category or kind of store associated with an entity, such as its retail or service type.
-
B.
storageOption
chosen
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
C.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
-
D.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
isMajorStorageFor
Indicates that one entity serves as the primary or main storage location or repository for 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a184870819084251554eae1e33c |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.