Triple
T4461530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigner crystal |
E98264
|
entity |
| Predicate | hasDimensionalVariant |
P455
|
FINISHED |
| Object | 2D Wigner crystal |
—
|
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: 2D Wigner crystal | Statement: [Wigner crystal, hasDimensionalVariant, 2D Wigner crystal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDimensionalVariant Context triple: [Wigner crystal, hasDimensionalVariant, 2D Wigner crystal]
-
A.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
B.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
C.
hasDimensionality
Indicates that an entity possesses a specific number of dimensions or a particular dimensional structure.
-
D.
includesDimension
Indicates that one entity encompasses or contains a particular dimension or measurable aspect as part of its definition or structure.
-
E.
hasDimensionParameter
Indicates that an entity is associated with a specific dimensional parameter (such as size, length, width, or height) that characterizes its measurable extent.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35674f718819089388c3924dd1414 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.