Triple
T11085795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voronin universality theorem |
E262116
|
entity |
| Predicate | approximationRegion |
P97139
|
FINISHED |
| Object | compact subsets of {s : 1/2 < Re(s) < 1} |
—
|
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: compact subsets of {s : 1/2 < Re(s) < 1} | Statement: [Voronin universality theorem, approximationRegion, compact subsets of {s : 1/2 < Re(s) < 1}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximationRegion
Context triple: [Voronin universality theorem, approximationRegion, compact subsets of {s : 1/2 < Re(s) < 1}]
-
A.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
B.
areaApprox
Indicates that one entity’s area is approximately equal to the area of another entity.
-
C.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
D.
approximateRadius
Indicates that one entity specifies or provides an estimated value for the radius of another entity.
-
E.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c2c7d4819087ac793153340178 |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.