Triple
T13651443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Néel vector |
E326746
|
entity |
| Predicate | orderParameterOf |
P110986
|
FINISHED |
| Object | antiferromagnetic 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: antiferromagnetic phase | Statement: [Néel vector, orderParameterOf, antiferromagnetic phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderParameterOf Context triple: [Néel vector, orderParameterOf, antiferromagnetic phase]
-
A.
orderParameter
Indicates the degree of structural or phase organization in a system, typically quantifying how ordered or coherent its state is relative to disorder.
-
B.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
C.
ordersBy
Indicates that one entity arranges, sorts, or sequences another entity according to a specified criterion or set of criteria.
-
D.
orderName
Indicates the designated name or label assigned to a specific order in a transaction or ordering process.
-
E.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
- 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_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. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:52 p.m.