Triple
T2407180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boiling Springs Lake |
E50302
|
entity |
| Predicate | hasCauseOfAcidity |
P708
|
FINISHED |
| Object | volcanic gases |
—
|
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: volcanic gases | Statement: [Boiling Springs Lake, hasCauseOfAcidity, volcanic gases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCauseOfAcidity Context triple: [Boiling Springs Lake, hasCauseOfAcidity, volcanic gases]
-
A.
acidityLevel
Indicates the degree or intensity of acidity associated with an entity, typically measured by pH or a comparable scale.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
hasStomachType
Indicates that an entity possesses or is characterized by a specific type or classification of stomach.
-
D.
hasCause
chosen
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
E.
hasHigherSalinityCause
Indicates that one condition, factor, or process is the cause of another having a higher level of salinity.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:58 p.m.