Triple
T379055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricci curvature tensor |
E8635
|
entity |
| Predicate | symmetryProperty |
P5685
|
FINISHED |
| Object | R_{ij} = R_{ji} |
—
|
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: R_{ij} = R_{ji} | Statement: [Ricci curvature tensor, symmetryProperty, R_{ij} = R_{ji}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symmetryProperty
Context triple: [Ricci curvature tensor, symmetryProperty, R_{ij} = R_{ji}]
-
A.
invariantUnder
Indicates that a property, structure, or quantity remains unchanged when a specified transformation or operation is applied.
-
B.
flowerSymmetry
Indicates the type or pattern of symmetry exhibited by a flower’s structure or arrangement of its parts.
-
C.
parity
Indicates that two quantities share the same evenness or oddness, or more generally that they have equivalent status or value in a given context.
-
D.
hasCurvatureInvariant
Indicates that one entity possesses a specific curvature-related invariant property or value associated with its geometric or mathematical structure.
-
E.
identifiesPropertyOf
chosen
Indicates that one entity specifies or denotes a particular property or attribute belonging to another entity.
- 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.