Triple
T23801769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nirenberg problem |
E588691
|
entity |
| Predicate | curvatureType |
P4461
|
FINISHED |
| Object | Gaussian curvature |
—
|
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: Gaussian curvature | Statement: [Nirenberg problem, curvatureType, Gaussian curvature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curvatureType Context triple: [Nirenberg problem, curvatureType, Gaussian curvature]
-
A.
usesCurvature
Indicates that one entity applies or relies on the curvature property or measure of another entity in its operation, definition, or analysis.
-
B.
hasCurvatureInvariant
chosen
Indicates that one entity possesses a specific curvature-related invariant property or value associated with its geometric or mathematical structure.
-
C.
isCurved
Indicates that an object or path deviates smoothly from a straight line, forming a bend or arc.
-
D.
allowsSpatialCurvature
Indicates that one entity permits or enables the presence or variation of spatial curvature in relation to another entity or context.
-
E.
hasCurvatureDivergence
Indicates that one entity exhibits a difference or variation in curvature relative to another entity or reference.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c74e430481909debd10c71785912 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:53 p.m.