Triple
T38012837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cumene process |
E948410
|
entity |
| Predicate | usesSeparation |
P176763
|
FINISHED |
| Object | fractional distillation |
—
|
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: fractional distillation | Statement: [cumene process, usesSeparation, fractional distillation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSeparation Context triple: [cumene process, usesSeparation, fractional distillation]
-
A.
typeOfSeparation
Indicates the specific manner or category of separation that exists or occurred between entities.
-
B.
usedToSeparate
chosen
Indicates that one entity serves as a means or tool to divide, isolate, or keep other entities apart from each other.
-
C.
definedSeparationFrom
Indicates a formally specified distinction or boundary established between one entity and another.
-
D.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
-
E.
separation
Indicates that one entity becomes or is kept apart from another entity or group, creating a distinct division or distance between them.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:20 p.m.