Triple
T36467876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ginibre ensemble |
E898467
|
entity |
| Predicate | entryVariance |
P27172
|
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: [Ginibre ensemble, entryVariance, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryVariance Context triple: [Ginibre ensemble, entryVariance, 1]
-
A.
hasVariance
chosen
Indicates that there is a measurable degree of variability or dispersion in the values or outcomes associated with the related entities.
-
B.
usesVAR
Indicates that one entity makes use of, employs, or utilizes another entity as a variable or resource in performing some function or operation.
-
C.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
D.
variesOver
Indicates that the value, state, or behavior of one entity changes as a function of another entity or parameter.
-
E.
varies
Indicates that the value, state, or condition of one entity changes in response to differences in another entity or context.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.