Triple
T1382514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian integers |
E29369
|
entity |
| Predicate | geometricStructure |
P25627
|
FINISHED |
| Object | square lattice in the complex plane |
—
|
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: square lattice in the complex plane | Statement: [Gaussian integers, geometricStructure, square lattice in the complex plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geometricStructure Context triple: [Gaussian integers, geometricStructure, square lattice in the complex plane]
-
A.
geometricFunction
Indicates a relationship where one entity serves as a geometric transformation or operation that, when applied, produces or modifies another geometric entity.
-
B.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
-
C.
hasGeometry
chosen
Indicates that an entity is associated with a specific geometric representation or spatial form.
-
D.
crystalStructure
Indicates the specific geometric arrangement of atoms or molecules in a crystalline material.
-
E.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3361bf08190b3f6bbf82e17685b |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.