Triple
T5782632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryan Mound storage site |
E128194
|
entity |
| Predicate | locatedInGeologicFormation |
P19734
|
FINISHED |
| Object | salt dome |
—
|
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: salt dome | Statement: [Bryan Mound storage site, locatedInGeologicFormation, salt dome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInGeologicFormation Context triple: [Bryan Mound storage site, locatedInGeologicFormation, salt dome]
-
A.
foundInGeologicSetting
chosen
Indicates that something occurs, is present, or has been discovered within a particular geological environment or context.
-
B.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
C.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
D.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
-
E.
stateOfFormation
Indicates the jurisdiction or region in which an entity was legally created or organized.
- 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.