Triple
T2523405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THC |
E55576
|
entity |
| Predicate | solubility |
P34779
|
FINISHED |
| Object | insoluble in 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: insoluble in water | Statement: [THC, solubility, insoluble in water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solubility Context triple: [THC, solubility, insoluble in 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.
dissolved
Indicates that one substance has been mixed into another so thoroughly that it forms a uniform solution and is no longer distinguishable as a separate phase.
-
C.
dissolutionTime
Indicates the point in time at which a relationship, structure, or entity ceases to exist or is formally terminated.
-
D.
predominantOxidationStateInSolution
Indicates the oxidation state that a chemical species most commonly or primarily adopts when present in a given solution.
-
E.
dissolutionProcess
Indicates the process or sequence of actions by which something (such as a substance, organization, or relationship) is broken down, disbanded, or brought to an end.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23a0a548190b44393e0f823f7a9 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.