Triple
T7338328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leech lattice |
E169185
|
entity |
| Predicate | kissingNumber |
P42025
|
FINISHED |
| Object | 196560 |
—
|
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: 196560 | Statement: [Leech lattice, kissingNumber, 196560]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kissingNumber Context triple: [Leech lattice, kissingNumber, 196560]
-
A.
dimensionCount
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
-
B.
dimensionAsVectorSpaceOverℚ
Indicates that the dimension of a given vector space is being considered specifically as a vector space over the field of rational numbers ℚ.
-
C.
dimension
Indicates that one entity specifies a measurable extent or size attribute (such as length, width, height, or similar quantitative property) of another entity.
-
D.
EulerCharacteristic
Indicates the topological invariant of a space that equals, in a suitable decomposition, the alternating sum of the counts of its cells (e.g., vertices − edges + faces).
-
E.
numberOfSpheres
chosen
Indicates the quantity of spheres associated with or contained by a given entity.
- 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_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. |
Created at: March 27, 2026, 3:04 p.m.