Triple
T26254248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griess algebra |
E656676
|
entity |
| Predicate | decompositionUnderMonster |
P43918
|
FINISHED |
| Object | 1 ⊕ 196883 |
—
|
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: 1 ⊕ 196883 | Statement: [Griess algebra, decompositionUnderMonster, 1 ⊕ 196883]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decompositionUnderMonster Context triple: [Griess algebra, decompositionUnderMonster, 1 ⊕ 196883]
-
A.
decomposesIn
Indicates that one entity breaks down or separates into another entity or set of entities as its components or products.
-
B.
decompositionType
chosen
Indicates the specific way in which a whole is broken down into its constituent parts or components.
-
C.
decomposesAbove
Indicates that one entity breaks down or disintegrates into parts or components that are located spatially above another entity.
-
D.
associatedWithMonster
Indicates a relationship in which an entity is connected or linked in some notable way to a monster.
-
E.
hasDecomposition
Indicates that something can be broken down or separated into constituent parts, components, or simpler elements.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcc29cc81908880bd825cb12141 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:08 p.m.