Triple
T35886656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Specialties, Aromatics and Styrenics |
E1037662
|
entity |
| Predicate | usesFeedstocksFrom |
P104219
|
FINISHED |
| Object | petrochemical processes |
—
|
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: petrochemical processes | Statement: [Specialties, Aromatics and Styrenics, usesFeedstocksFrom, petrochemical processes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFeedstocksFrom Context triple: [Specialties, Aromatics and Styrenics, usesFeedstocksFrom, petrochemical processes]
-
A.
usesFeedstock
chosen
Indicates that one entity employs or consumes another entity as a raw material or input resource in a process or operation.
-
B.
isFedBy
Indicates that one entity receives nourishment, food, or sustenance from another entity.
-
C.
usedFeederFunds
Indicates that an entity employed feeder funds as intermediary investment vehicles to channel capital into another fund or investment structure.
-
D.
usesTargetsFrom
Indicates that one entity selects or operates on targets that are defined, provided, or referenced by another entity.
-
E.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:06 p.m.