Triple
T21001252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shah sour gas field |
E517293
|
entity |
| Predicate | sulfurUse |
P95765
|
FINISHED |
| Object | fertilizer production |
—
|
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: fertilizer production | Statement: [Shah sour gas field, sulfurUse, fertilizer production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sulfurUse Context triple: [Shah sour gas field, sulfurUse, fertilizer production]
-
A.
typicalSulfurLimit
Indicates the usual or standard upper bound on the amount of sulfur allowed or present in a given context.
-
B.
hasSulfurOdor
Indicates that an entity emits or possesses an odor characteristic of sulfur or sulfur-containing compounds.
-
C.
sulfurRecoveryProcess
chosen
Indicates a process in which sulfur is recovered or extracted, typically from industrial streams or waste gases.
-
D.
coalUse
Indicates the use or consumption of coal by an entity, typically as a fuel or energy source.
-
E.
usesChemistry
Indicates that one entity applies or relies on chemistry, chemical methods, or chemical principles in relation to another entity or context.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc25c1f8819086bdbfd89d390f5f |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.