Triple
T26468667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Vleck paramagnetism |
E665838
|
entity |
| Predicate | susceptibilitySign |
P24994
|
FINISHED |
| Object | positive |
—
|
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: positive | Statement: [Van Vleck paramagnetism, susceptibilitySign, positive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: susceptibilitySign Context triple: [Van Vleck paramagnetism, susceptibilitySign, positive]
-
A.
susceptibleTo
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
B.
showsSignOf
Indicates that one entity exhibits evidence, symptoms, or characteristics suggesting the presence or occurrence of another entity, condition, or state.
-
C.
clinicalSignOf
Indicates that one clinical sign is evidence or manifestation of a particular disease, condition, or underlying medical state.
-
D.
isSuspiciousOf
Indicates that one entity believes another entity or situation may be untrustworthy, harmful, or involved in wrongdoing.
-
E.
sensitivityFeature
chosen
Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612c5f208819096a791c6a90dc571 |
completed | May 2, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:17 a.m.