Triple
T14773608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London dispersion forces |
E347195
|
entity |
| Predicate | increaseWith |
P35660
|
FINISHED |
| Object | increasing molar mass |
—
|
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: increasing molar mass | Statement: [London dispersion forces, increaseWith, increasing molar mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: increaseWith Context triple: [London dispersion forces, increaseWith, increasing molar mass]
-
A.
increasesWith
chosen
Indicates that as the value or magnitude of one entity grows, the value or magnitude of another entity correspondingly grows as well.
-
B.
increases
Indicates that one entity causes another entity’s value, level, or intensity to become larger or higher.
-
C.
subsequentIncrease
Indicates that one quantity or value increases after a prior event, state, or change has occurred.
-
D.
usesIncrement
Indicates that one entity applies or relies on an increment operation or incremental value derived from another entity.
-
E.
firstIncreaseIn
Indicates the point or event at which a quantity or value begins to increase for the first time in a given sequence 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81485e08190be35baafcf22b6f2 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.