Triple
T17752841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian orthogonal ensemble |
E443153
|
entity |
| Predicate | timeReversalSymmetry |
P47525
|
FINISHED |
| Object | present |
—
|
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: present | Statement: [Gaussian orthogonal ensemble, timeReversalSymmetry, present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeReversalSymmetry Context triple: [Gaussian orthogonal ensemble, timeReversalSymmetry, present]
-
A.
timeSymmetry
chosen
Indicates that a process or relationship remains valid and unchanged when the direction of time is reversed.
-
B.
reversibility
Indicates that a process, action, or transformation can be undone or reversed to restore the original state or conditions.
-
C.
symmetryInvolved
Indicates that a relationship or action inherently involves symmetry, such as invariance under certain transformations or the presence of symmetric structure or behavior.
-
D.
symmetryChange
Indicates a change in the symmetry properties of an entity or system, such as gaining, losing, or altering its symmetry.
-
E.
timePeriodReflected
Indicates that one entity represents or corresponds to the time period associated with another entity.
- 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.