Triple
T32870564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignicoccus |
E840776
|
entity |
| Predicate | usesSulfurReduction |
P192855
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ignicoccus, usesSulfurReduction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSulfurReduction Context triple: [Ignicoccus, usesSulfurReduction, true]
-
A.
sulfurRecoveryProcess
Indicates a process in which sulfur is recovered or extracted, typically from industrial streams or waste gases.
-
B.
typicalSulfurLimit
Indicates the usual or standard upper bound on the amount of sulfur allowed or present in a given context.
-
C.
nitrateReduction
Indicates that a process or agent converts nitrate into a more reduced nitrogen form, such as nitrite, ammonia, or nitrogen gas.
-
D.
sulfurOxidationProduct
Indicates that one entity is a product resulting from the oxidation of a sulfur-containing substance.
-
E.
isReducedDuringUseTo
Indicates that the quantity, intensity, or effectiveness of one entity decreases as a direct result of being used or consumed.
- F. None of above. chosen
Provenance (4 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: May 1, 2026, 1:17 a.m.