Triple
T17798344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian symplectic ensemble |
E444351
|
entity |
| Predicate | isOneOfDysonThreefoldWay |
P128955
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gaussian symplectic ensemble, isOneOfDysonThreefoldWay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfDysonThreefoldWay Context triple: [Gaussian symplectic ensemble, isOneOfDysonThreefoldWay, yes]
-
A.
DysonIndexValue
Indicates the numerical value assigned to represent a Dyson-related metric or index for an entity or system.
-
B.
hasThreeVolumeStructureRole
Indicates that an entity participates in or fulfills a role within a three-volume structural organization or framework.
-
C.
isThreeWayRace
Indicates that a race or competition involves exactly three participants or entities competing against each other.
-
D.
has3DVersion
Indicates that an entity has a corresponding three-dimensional (3D) version or representation.
-
E.
haveDualityProperty
Indicates that an entity possesses a characteristic or state that inherently consists of two complementary, contrasting, or coexisting aspects.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fcfdc8819086f41152860dfe18 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:13 a.m.