Triple
T10991721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riemann sphere |
E259767
|
entity |
| Predicate | topologicallyEquivalentTo |
P73738
|
FINISHED |
| Object | 2-sphere |
—
|
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: 2-sphere | Statement: [Riemann sphere, topologicallyEquivalentTo, 2-sphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topologicallyEquivalentTo Context triple: [Riemann sphere, topologicallyEquivalentTo, 2-sphere]
-
A.
homeomorphicTo
chosen
Indicates that two topological spaces can be continuously deformed into each other via a bijective, continuous map with a continuous inverse, preserving their topological structure.
-
B.
isTopological
Indicates that something possesses the properties or structure required to be considered a topology in the relevant mathematical or spatial context.
-
C.
hasSameBoundariesAs
Indicates that two entities share identical spatial or conceptual boundaries, matching each other exactly in extent and limits.
-
D.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
E.
typicalTopology
Indicates the usual or most common network or structural arrangement that characterizes how the related entities are organized or interconnected.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d795d1e918819090c71f5a077fa15a |
completed | April 9, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.