Triple
T33578955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobian variety |
E860099
|
entity |
| Predicate | hasLattice |
P59520
|
FINISHED |
| Object | period lattice |
—
|
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: period lattice | Statement: [Jacobian variety, hasLattice, period lattice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLattice Context triple: [Jacobian variety, hasLattice, period lattice]
-
A.
hasLatticeStructure
Indicates that one entity possesses or exhibits a lattice structure, meaning its elements are partially ordered such that any two elements have well-defined least upper and greatest lower bounds.
-
B.
isLatticeIn
Indicates that one structure forms a lattice within, or relative to, another structure or context.
-
C.
latticeRequirement
Indicates that one entity must satisfy a specified lattice-theoretic condition or structure requirement in relation to another.
-
D.
havePeriodLattice
chosen
Indicates that one entity possesses or is associated with a specific period lattice structure.
-
E.
hasLatticeSubgroups
Indicates that one mathematical structure contains subgroups that form a lattice under inclusion or related order operations.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 1, 2026, 1:40 a.m.