Triple
T17752842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian orthogonal ensemble |
E443153
|
entity |
| Predicate | betaEnsembleParameter |
P97142
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Gaussian orthogonal ensemble, betaEnsembleParameter, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betaEnsembleParameter Context triple: [Gaussian orthogonal ensemble, betaEnsembleParameter, 1]
-
A.
parametrizes
chosen
Indicates that one entity defines or controls the variable parameters that determine the behavior, form, or configuration of another entity.
-
B.
ensembleSize
Indicates the number of individual members or participants that make up a given group or ensemble.
-
C.
mainEnsemble
Indicates that an entity serves as the primary or central ensemble associated with another entity (such as a work, performance, or production).
-
D.
requiresEnsemble
Indicates that performing or realizing one entity necessitates the coordinated participation of multiple entities acting together as an ensemble.
-
E.
typeOfEnsemble
Indicates the specific kind or category of ensemble that an entity belongs to or represents.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841c0540819093a32d759775c61f |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.