Triple
T18376817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oltu stone deposits |
E446338
|
entity |
| Predicate | combustibility |
P39894
|
FINISHED |
| Object | combustible organic material |
—
|
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: combustible organic material | Statement: [Oltu stone deposits, combustibility, combustible organic material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combustibility Context triple: [Oltu stone deposits, combustibility, combustible organic material]
-
A.
isCombustible
chosen
Indicates that a substance or material is capable of catching fire and burning under certain conditions.
-
B.
combustionType
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
-
C.
combustionProperty
Indicates a relationship where an entity is characterized by how it behaves in combustion, such as its flammability, ignition conditions, or burning behavior.
-
D.
isLessFlammableThan
Indicates that one entity has a lower tendency to catch fire or burn than another entity.
-
E.
burnCapability
Indicates that an entity has the ability or potential to burn, ignite, or cause combustion under certain conditions.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179849d08190a3ffb9edc633d2ee |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.