Triple
T17798340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian symplectic ensemble |
E444351
|
entity |
| Predicate | hasDysonIndex |
P55561
|
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, hasDysonIndex, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDysonIndex Context triple: [Gaussian symplectic ensemble, hasDysonIndex, 4]
-
A.
DysonIndexValue
chosen
Indicates the numerical value assigned to represent a Dyson-related metric or index for an entity or system.
-
B.
hasDynamics
Indicates that one entity exhibits or is characterized by specific dynamic behavior, changes, or variations over time in relation to another entity or context.
-
C.
numberOfDynamos
Indicates the quantity of dynamos associated with or contained by a given entity.
-
D.
DysonBubbleDefinition
Indicates the conceptual specification or characterization of a Dyson bubble structure and how its components are arranged or function together.
-
E.
canIndex
Indicates that one entity has the capability or permission to create, maintain, or use an index over another entity (such as data, documents, or resources) for efficient access or retrieval.
- 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.