Triple
T19376995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La2CuO4 |
E484697
|
entity |
| Predicate | spaceGroup |
P135715
|
FINISHED |
| Object | I4/mmm (high temperature) |
—
|
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: I4/mmm (high temperature) | Statement: [La2CuO4, spaceGroup, I4/mmm (high temperature)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceGroup Context triple: [La2CuO4, spaceGroup, I4/mmm (high temperature)]
-
A.
crystalSystem
Indicates the crystallographic lattice system or symmetry category to which a crystal or mineral belongs.
-
B.
crystalStructure
Indicates the specific geometric arrangement of atoms or molecules in a crystalline material.
-
C.
usesSymmetryGroup
Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
-
D.
isMaximalSymmetryGroupOf
Indicates that a group represents the largest possible symmetry group for a given object or structure, such that no strictly larger symmetry group of that object exists containing it.
-
E.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
- 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_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. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:35 p.m.