Triple
T18605118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullicame springs |
E454722
|
entity |
| Predicate | hasChemicalComponent |
P24581
|
FINISHED |
| Object | sulfur |
—
|
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: sulfur | Statement: [Bullicame springs, hasChemicalComponent, sulfur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChemicalComponent Context triple: [Bullicame springs, hasChemicalComponent, sulfur]
-
A.
chemicalComponent
Indicates that one entity is a constituent chemical part or ingredient of another entity.
-
B.
containsChemical
chosen
Indicates that one entity includes or has within it a specified chemical substance.
-
C.
hasChemicalProperty
Indicates that an entity possesses or exhibits a specific chemical property or characteristic.
-
D.
hasChemicalClass
Indicates that an entity belongs to, or is categorized under, a particular chemical class based on its structural or compositional characteristics.
-
E.
hasChemicalFormula
Indicates that one entity (typically a chemical substance) is characterized by or associated with a specific chemical formula representing its elemental composition.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e547535b8c8190ab5a8a92f15f2bcb |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.