Triple
T4389289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP-1 |
E99321
|
entity |
| Predicate | combustionProperty |
P56321
|
FINISHED |
| Object | producesSoot |
—
|
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: producesSoot | Statement: [RP-1, combustionProperty, producesSoot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combustionProperty Context triple: [RP-1, combustionProperty, producesSoot]
-
A.
combustionType
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
-
B.
combustionChamber
Indicates that one entity functions as the combustion chamber in which another entity’s fuel–air mixture is burned to produce energy or propulsion.
-
C.
isCombustible
Indicates that a substance or material is capable of catching fire and burning under certain conditions.
-
D.
burnMechanism
Indicates the process or mechanism by which burning or combustion occurs or is carried out.
-
E.
ignitionMethod
Indicates the specific way or mechanism by which something is ignited or set on fire.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35281900c8190882e9ccfa44ab86f |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.