Triple
T11729488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lewisite |
E278861
|
entity |
| Predicate | decomposesIn |
P101028
|
FINISHED |
| Object | alkaline solutions |
—
|
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: alkaline solutions | Statement: [lewisite, decomposesIn, alkaline solutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decomposesIn Context triple: [lewisite, decomposesIn, alkaline solutions]
-
A.
hasDecomposition
Indicates that something can be broken down or separated into constituent parts, components, or simpler elements.
-
B.
decompositionType
Indicates the specific way in which a whole is broken down into its constituent parts or components.
-
C.
decomposesAbove
Indicates that one entity breaks down or disintegrates into parts or components that are located spatially above another entity.
-
D.
yieldsDecomposition
Indicates that one entity produces or results in a particular breakdown or decomposition of another entity.
-
E.
canBeDissectedBy
Indicates that one entity is capable of being divided or analyzed into parts by another entity or method.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d80ef881908cab956787ab07fd |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.