Triple
T26253947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E8 lattice |
E656669
|
entity |
| Predicate | hasRootSystemSize |
P169230
|
FINISHED |
| Object | 240 |
—
|
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: 240 | Statement: [E8 lattice, hasRootSystemSize, 240]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRootSystemSize Context triple: [E8 lattice, hasRootSystemSize, 240]
-
A.
hasRootSystem
Indicates that one entity possesses or is characterized by a particular type of root system.
-
B.
hasSizeSystem
Indicates that an entity is associated with or defined according to a particular size measurement system.
-
C.
isRootOf
Indicates that one entity is the root or origin point from which another entity directly or indirectly descends or is derived.
-
D.
hasRootsOfNorm
Indicates that one entity possesses or is associated with roots (e.g., solutions or base elements) whose norm satisfies a specified condition or value in relation to another entity.
-
E.
hasWellAtRoot
Indicates that an entity possesses or has a well located at its root or base.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 26, 2026, 9:08 p.m.