Triple
T13651445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Néel vector |
E326746
|
entity |
| Predicate | nonZeroIn |
P9151
|
FINISHED |
| Object | antiferromagnetically ordered phase |
—
|
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: antiferromagnetically ordered phase | Statement: [Néel vector, nonZeroIn, antiferromagnetically ordered phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonZeroIn Context triple: [Néel vector, nonZeroIn, antiferromagnetically ordered phase]
-
A.
isNonzeroFor
chosen
Indicates that a given value, function, or quantity is not equal to zero under specified conditions or for specified inputs.
-
B.
isNonZeroBecause
Indicates that a value is non-zero specifically due to the stated cause, reason, or contributing factor.
-
C.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
D.
isNonNegative
Indicates that a value is greater than or equal to zero.
-
E.
hasIndependentDigitZero
Indicates that an entity possesses at least one digit or numeral component that is a zero considered as a distinct, standalone element.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc609676c8190b5b1cabe6b315142 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.