Triple
T34295718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daisetta, Texas |
E880019
|
entity |
| Predicate | landSubsidenceCause |
P77074
|
FINISHED |
| Object | salt dome and subsurface instability |
—
|
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 and subsurface instability | Statement: [Daisetta, Texas, landSubsidenceCause, salt dome and subsurface instability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landSubsidenceCause Context triple: [Daisetta, Texas, landSubsidenceCause, salt dome and subsurface instability]
-
A.
subsidenceMechanism
chosen
Indicates the process or mechanism by which ground or surface subsidence occurs.
-
B.
subsidenceMitigation
Indicates actions or measures taken to prevent, reduce, or control ground subsidence and its impacts.
-
C.
causeOfSediment
Indicates that one entity is the source or generating factor responsible for the formation or presence of sediment in another entity or location.
-
D.
landslideProne
Indicates that an area or location is susceptible to experiencing landslides under certain conditions.
-
E.
seismicityCause
Indicates that one factor or event is the cause or source of observed seismic activity in another context or location.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.