Triple
T379048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricci curvature tensor |
E8635
|
entity |
| Predicate | traceWithRespectTo |
P12683
|
FINISHED |
| Object | metric tensor |
—
|
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: metric tensor | Statement: [Ricci curvature tensor, traceWithRespectTo, metric tensor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traceWithRespectTo Context triple: [Ricci curvature tensor, traceWithRespectTo, metric tensor]
-
A.
formerTraversal
Indicates that one entity previously traversed, passed through, or traveled along another entity, but is no longer doing so.
-
B.
calledBy
Indicates that one entity initiates a call or invocation to another entity.
-
C.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
D.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
E.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a2eae0bd7081908197bbf5c55fe647 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.