Triple
T378912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski space-time |
E8632
|
entity |
| Predicate | curvature |
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: [Minkowski space-time, curvature, zero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curvature Context triple: [Minkowski space-time, curvature, zero]
-
A.
hasCurvatureInvariant
chosen
Indicates that one entity possesses a specific curvature-related invariant property or value associated with its geometric or mathematical structure.
-
B.
hasCurvatureDivergence
Indicates that one entity exhibits a difference or variation in curvature relative to another entity or reference.
-
C.
allowsSpatialCurvature
Indicates that one entity permits or enables the presence or variation of spatial curvature in relation to another entity or context.
-
D.
hasGeodesics
Indicates that the subject possesses or is characterized by geodesic paths, typically representing shortest or straightest possible routes within a given space or geometry.
-
E.
circumference
Indicates the total length around the boundary of a closed curve, typically a circle, relating a shape to the measure of its perimeter.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2974988190a1d6316cbb5159c8 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.