Triple
T14773603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London dispersion forces |
E347195
|
entity |
| Predicate | existEvenIn |
P9000
|
FINISHED |
| Object | nonpolar substances |
—
|
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: nonpolar substances | Statement: [London dispersion forces, existEvenIn, nonpolar substances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existEvenIn Context triple: [London dispersion forces, existEvenIn, nonpolar substances]
-
A.
existsIf
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
B.
existsFor
chosen
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
C.
existsOnlyAs
Indicates that the subject exists solely in a particular form, state, or context specified by the object, and not in any other.
-
D.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
E.
hasExistentiale
Indicates that an entity possesses or is associated with an existential characteristic, condition, or mode of being.
- 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.