Triple
T36878737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bromo-Seltzer |
E911414
|
entity |
| Predicate | isDissolvedIn |
P34779
|
FINISHED |
| Object | water |
—
|
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: water | Statement: [Bromo-Seltzer, isDissolvedIn, water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDissolvedIn Context triple: [Bromo-Seltzer, isDissolvedIn, water]
-
A.
canBeDissolvedWith
chosen
Indicates that one entity is capable of being dissolved or broken down when exposed to another specified substance or medium.
-
B.
canDissolveWith
Indicates that one substance is capable of dissolving another substance when they are combined.
-
C.
isInsolubleIn
Indicates that one substance does not dissolve in another under specified conditions.
-
D.
mayBeDissolvedBy
Indicates that one entity has the potential or capability to dissolve another entity.
-
E.
canBeDissolvedWhen
Indicates that one substance is capable of dissolving under the specific conditions, time, or circumstances denoted by the related entity or event.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.