Triple
T21953499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borel subalgebras |
E542124
|
entity |
| Predicate | containment |
P146682
|
FINISHED |
| Object | contain a Cartan subalgebra |
—
|
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: contain a Cartan subalgebra | Statement: [Borel subalgebras, containment, contain a Cartan subalgebra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containment Context triple: [Borel subalgebras, containment, contain a Cartan subalgebra]
-
A.
containmentStructure
Indicates that one entity serves as a physical or logical container or enclosing structure for another entity.
-
B.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
C.
containmentVenting
Indicates a relationship where a containment system releases or vents its contents, typically to relieve pressure or prevent overaccumulation.
-
D.
primaryContainmentType
Indicates the main method or structure used to hold, enclose, or confine one entity within another.
-
E.
contention
Indicates a state of active disagreement, dispute, or conflict between entities over an issue, claim, or resource.
- 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_69f1243dfb4081909bc7a722843ffea7 |
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.