Triple
T14619224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Fuel Additives Company |
E343171
|
entity |
| Predicate | hasChemicalProduct |
P3585
|
FINISHED |
| Object | methyl tert-butyl ether |
—
|
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: methyl tert-butyl ether | Statement: [Qatar Fuel Additives Company, hasChemicalProduct, methyl tert-butyl ether]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChemicalProduct Context triple: [Qatar Fuel Additives Company, hasChemicalProduct, methyl tert-butyl ether]
-
A.
containsChemical
Indicates that one entity includes or has within it a specified chemical substance.
-
B.
chemicalTypeProduced
Indicates that a process, reaction, or entity results in the production of a specific type or class of chemical.
-
C.
hasProduct
chosen
Indicates that an entity possesses, offers, or is associated with a particular product.
-
D.
hasChemicalProperty
Indicates that an entity possesses or exhibits a specific chemical property or characteristic.
-
E.
hasChemicalClass
Indicates that an entity belongs to, or is categorized under, a particular chemical class based on its structural or compositional characteristics.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46550e48190af45f426f02579bb |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.