Triple
T6295461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lie bracket |
E141120
|
entity |
| Predicate | antisymmetryCondition |
P69855
|
FINISHED |
| Object | [x,y] = -[y,x] |
—
|
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: [x,y] = -[y,x] | Statement: [Lie bracket, antisymmetryCondition, [x,y] = -[y,x]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antisymmetryCondition Context triple: [Lie bracket, antisymmetryCondition, [x,y] = -[y,x]]
-
A.
bracketIsAntisymmetric
chosen
Indicates that the bracket operation changes sign when its two arguments are swapped, so [x, y] = −[y, x].
-
B.
asymmetric
Indicates that the relationship between two entities never holds in both directions simultaneously, so if it holds from A to B it cannot also hold from B to A.
-
C.
equalityCondition
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
-
D.
canBeAsymmetricBetween
Indicates that the relationship or property may hold in one direction between two entities without necessarily holding in the reverse direction.
-
E.
afterSymmetryBreakingGives
Indicates that one entity or state results from another specifically after a symmetry-breaking process has occurred.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06439a6908190b0a8ebf426d3ca02 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.