Triple
T30327330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle Limit I |
E771376
|
entity |
| Predicate | tessellationType |
P168848
|
FINISHED |
| Object | hyperbolic tessellation |
—
|
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: hyperbolic tessellation | Statement: [Circle Limit I, tessellationType, hyperbolic tessellation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tessellationType Context triple: [Circle Limit I, tessellationType, hyperbolic tessellation]
-
A.
shapeType
Indicates the specific geometric form or category that characterizes an entity’s shape.
-
B.
textureType
Indicates the specific kind or category of surface quality or feel that characterizes an entity.
-
C.
glazingPattern
Indicates the arrangement or design pattern of glazing elements (such as panes or glass sections) within a structure or object.
-
D.
triskelionType
Indicates that one entity is classified as a specific type or variant of a triskelion.
-
E.
hasPavementPattern
Indicates that an entity possesses or is characterized by a specific pattern or design in its pavement surface.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681c48ffc819098fa0303a15f2114 |
completed | May 2, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:53 p.m.