Triple
T2364540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riemann mapping theorem |
E47349
|
entity |
| Predicate | hasCanonicalTarget |
P14889
|
FINISHED |
| Object | open unit disk |
—
|
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: open unit disk | Statement: [Riemann mapping theorem, hasCanonicalTarget, open unit disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalTarget Context triple: [Riemann mapping theorem, hasCanonicalTarget, open unit disk]
-
A.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
B.
hasTarget
chosen
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
C.
hasCanonicalLocation
Indicates that an entity is associated with its primary, standard, or officially recognized location.
-
D.
hasCanonicalPosition
Indicates that an entity occupies a standard, officially recognized, or authoritative position or location within a defined structure or system.
-
E.
hasCanonicalNumber
Indicates that an entity is associated with its officially recognized or standard reference number.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc7486cb48190acef1891cc87bdb1 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.