Triple
T36094693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulphur Springs |
E1044023
|
entity |
| Predicate | primaryGas |
P22265
|
FINISHED |
| Object | hydrogen sulphide |
—
|
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: hydrogen sulphide | Statement: [Sulphur Springs, primaryGas, hydrogen sulphide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGas Context triple: [Sulphur Springs, primaryGas, hydrogen sulphide]
-
A.
typeOfGasUsed
Indicates the specific kind of gas that is utilized in relation to an entity or process.
-
B.
primaryHydrocarbon
Indicates that one entity is a primary hydrocarbon, typically meaning it has a carbon atom bonded to only one other carbon within the molecular structure.
-
C.
gasContent
chosen
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
D.
gasSystem
Indicates a relationship where an entity functions as, is part of, or is associated with a gas-based system used for distribution, control, or processing of gases.
-
E.
primaryHydrocarbonType
Indicates the main or dominant type of hydrocarbon associated with an entity, such as a resource, sample, or reservoir.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.