Triple
T19377000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La2CuO4 |
E484697
|
entity |
| Predicate | magneticOrder |
P133533
|
FINISHED |
| Object | antiferromagnetic |
—
|
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 | Statement: [La2CuO4, magneticOrder, antiferromagnetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magneticOrder Context triple: [La2CuO4, magneticOrder, antiferromagnetic]
-
A.
magneticOrdering
chosen
Indicates the type of magnetic alignment or arrangement that exists between the magnetic moments of entities in a material or system.
-
B.
magneticInteraction
Indicates a relationship in which entities exert forces or influences on each other due to their magnetic fields or magnetic properties.
-
C.
magneticActivity
Indicates a relationship where an entity exhibits, causes, or is characterized by magnetic phenomena such as fields, storms, or fluctuations.
-
D.
magneticCharge
Indicates that an entity possesses a specified magnetic charge or is associated with a particular quantity or type of magnetic charge.
-
E.
magnetizationArisesFrom
Indicates that a magnetization property or state is caused or generated by a specified underlying process, structure, or source.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5cfbf48190ac60e3ffa6baa263 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.