Triple
T24652697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochow process |
E610296
|
entity |
| Predicate | catalystPromoter |
P157161
|
FINISHED |
| Object | arsenic |
—
|
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: arsenic | Statement: [Rochow process, catalystPromoter, arsenic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalystPromoter Context triple: [Rochow process, catalystPromoter, arsenic]
-
A.
catalystPromoter
chosen
Indicates that one entity enhances or facilitates the catalytic activity or effectiveness of another entity.
-
B.
catalyst
Indicates that one entity facilitates or accelerates a process, reaction, or change involving another entity without itself being consumed or fundamentally altered.
-
C.
catalystGeneration
Indicates that one entity initiates, produces, or brings about a catalyst that enables or accelerates a process or reaction involving another entity.
-
D.
catalystRegenerated
Indicates that a catalyst, after facilitating a reaction, is restored to its original state and made available to participate in the reaction cycle again.
-
E.
typicalCatalystLoading
Indicates the usual amount or concentration of catalyst employed in a given reaction or process.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 2:34 a.m.