Triple
T26468666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Vleck paramagnetism |
E665838
|
entity |
| Predicate | fieldRegime |
P163449
|
FINISHED |
| Object | usually treated in low-field limit |
—
|
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: usually treated in low-field limit | Statement: [Van Vleck paramagnetism, fieldRegime, usually treated in low-field limit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldRegime Context triple: [Van Vleck paramagnetism, fieldRegime, usually treated in low-field limit]
-
A.
fieldDivision
Indicates a relationship where a larger field or area is partitioned into smaller sections or subdivisions.
-
B.
regulatoryField
Indicates that one entity operates within, is governed by, or is associated with a particular area or domain of regulation defined by another entity.
-
C.
fieldOfOperation
Indicates the domain, area, or scope within which an entity operates or carries out its primary activities.
-
D.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
E.
fields
Indicates that one entity has fields or attributes that are defined, declared, or contained within another entity.
- F. None of above. chosen
Provenance (4 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_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 12:17 a.m.