Triple
T27176444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sl(2,C) |
E683055
|
entity |
| Predicate | bracketOperation |
P69866
|
FINISHED |
| Object | matrix commutator |
—
|
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: matrix commutator | Statement: [sl(2,C), bracketOperation, matrix commutator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bracketOperation Context triple: [sl(2,C), bracketOperation, matrix commutator]
-
A.
hasBracket
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
-
B.
usesBracket
Indicates that one entity employs or incorporates a bracket as a structural or functional component in relation to another entity.
-
C.
bracketNotNecessarilyAssociative
chosen
Indicates that the bracketing operation on elements does not in general satisfy the associative law, so changing the grouping of operands can change the result.
-
D.
numberOfBrackets
Indicates the count of brackets associated with or contained in a given entity or structure.
-
E.
operatorSymbol
Indicates the symbolic notation used to represent an operator in an expression or formal system.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6257a5ae881908db3032511378836 |
completed | May 2, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:26 a.m.