Triple
T7338323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leech lattice |
E169185
|
entity |
| Predicate | isIntegral |
P77155
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Leech lattice, isIntegral, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntegral Context triple: [Leech lattice, isIntegral, true]
-
A.
isIntegralOver
Indicates that one algebraic structure (typically a ring element or extension) satisfies a monic polynomial with coefficients in another ring, expressing that it is algebraically dependent on and “integral over” that base ring.
-
B.
hasIntegralRepresentation
Indicates that one entity can be expressed or represented as an integral involving the other entity.
-
C.
isInteger
Indicates that a given value represents a whole number with no fractional or decimal component.
-
D.
isIntegralFormOf
Indicates that one entity is the integral (indefinite integral or antiderivative) form corresponding to another entity, typically a derivative or differential expression.
-
E.
isIntegerUnitIn
Indicates that one integer-valued unit is contained within, or belongs to, a specified larger unit or unit set.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f3463d0481908aed9ed43a8ac6a8 |
completed | March 27, 2026, 9:14 p.m. |
Created at: March 27, 2026, 3:04 p.m.