Triple
T2364451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riemann surface |
E47348
|
entity |
| Predicate | realDimension |
P6122
|
FINISHED |
| Object | two real dimensions |
—
|
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: two real dimensions | Statement: [Riemann surface, realDimension, two real dimensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realDimension Context triple: [Riemann surface, realDimension, two real dimensions]
-
A.
externalDimension
Indicates that an entity has a measurable size or extent along one or more outer spatial dimensions (such as length, width, or height).
-
B.
dimensionCount
chosen
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
-
C.
dimension
Indicates that one entity specifies a measurable extent or size attribute (such as length, width, height, or similar quantitative property) of another entity.
-
D.
dimensionOfComponents
Indicates that a specified dimension value is associated with, or applies to, the components of an object or system.
-
E.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
- 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.