Triple
T28572710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bechamp reduction |
E723154
|
entity |
| Predicate | productExample |
P186366
|
FINISHED |
| Object | p-phenylenediamine |
—
|
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: p-phenylenediamine | Statement: [Bechamp reduction, productExample, p-phenylenediamine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productExample Context triple: [Bechamp reduction, productExample, p-phenylenediamine]
-
A.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
B.
productForm
Indicates the specific physical or presentation format in which a product is offered or delivered (e.g., tablet, liquid, package type).
-
C.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
D.
productIndex
Indicates the position or ordering of a product within a sequence, list, or collection.
-
E.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving another entity.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 28, 2026, 4:10 a.m.