Triple
T17798341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian symplectic ensemble |
E444351
|
entity |
| Predicate | hasDysonClassLabel |
P9248
|
FINISHED |
| Object | β = 4 |
—
|
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: β = 4 | Statement: [Gaussian symplectic ensemble, hasDysonClassLabel, β = 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDysonClassLabel Context triple: [Gaussian symplectic ensemble, hasDysonClassLabel, β = 4]
-
A.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
hasLabel
chosen
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
-
C.
hasDynamicalClass
Indicates that an entity belongs to a specific category defined by its dynamical or motion-related behavior (e.g., orbital or kinematic characteristics).
-
D.
hasDuneType
Indicates that one entity is characterized by or associated with a specific type or classification of dune.
-
E.
hasEponymousLabel
Indicates that something is named after a particular person, place, or entity, serving as its eponym.
- 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_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. |
Created at: April 10, 2026, 10:13 a.m.