Triple
T21953168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartan–Killing form |
E542117
|
entity |
| Predicate | isCanonicalOn |
P146678
|
FINISHED |
| Object | semisimple Lie algebra |
—
|
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: semisimple Lie algebra | Statement: [Cartan–Killing form, isCanonicalOn, semisimple Lie algebra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCanonicalOn Context triple: [Cartan–Killing form, isCanonicalOn, semisimple Lie algebra]
-
A.
isCanonical
Indicates that something represents the standard, authoritative, or officially accepted form within a given context or system.
-
B.
isCanonicalFormOf
Indicates that one entity is the standard or officially accepted form or representation of another, often more variant, entity.
-
C.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
-
D.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
E.
isCanonicalZone
Indicates that a given zone is the primary, standard, or officially recognized version among possible alternatives.
- F. None of above. chosen
Provenance (4 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243d43d8819084e280b129631288 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb9b75308190addc3dba7b5d5ddd |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:59 p.m.