Triple
T34585645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S^2 × R geometry |
E888036
|
entity |
| Predicate | hasCurvatureInRDirection |
P4461
|
FINISHED |
| Object | zero |
—
|
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: zero | Statement: [S^2 × R geometry, hasCurvatureInRDirection, zero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurvatureInRDirection Context triple: [S^2 × R geometry, hasCurvatureInRDirection, zero]
-
A.
hasCurvatureBehavior
Indicates how the curvature of an object or path behaves or changes under specified conditions or over a given domain.
-
B.
hasCurvatureInvariant
chosen
Indicates that one entity possesses a specific curvature-related invariant property or value associated with its geometric or mathematical structure.
-
C.
curvatureCondition
Indicates that a specified geometric object or path satisfies a particular constraint or requirement on its curvature.
-
D.
hasCurvatureDivergence
Indicates that one entity exhibits a difference or variation in curvature relative to another entity or reference.
-
E.
usesCurvature
Indicates that one entity applies or relies on the curvature property or measure of another entity in its operation, definition, or analysis.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 1, 2026, 2:03 a.m.