Triple
T379063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricci curvature tensor |
E8635
|
entity |
| Predicate | vanishesFor |
P9150
|
FINISHED |
| Object | flat manifold |
—
|
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: flat manifold | Statement: [Ricci curvature tensor, vanishesFor, flat manifold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vanishesFor Context triple: [Ricci curvature tensor, vanishesFor, flat manifold]
-
A.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
B.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
D.
withdrewFrom
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
-
E.
isZeroFor
chosen
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
- 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.