Triple

T461770
Position Surface form Disambiguated ID Type / Status
Subject Einstein tensor E7353 entity
Predicate definedInTermsOf P3573 FINISHED
Object Riemann curvature tensor via contractions 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: Riemann curvature tensor via contractions | Statement: [Einstein tensor, definedInTermsOf, Riemann curvature tensor via contractions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definedInTermsOf
Context triple: [Einstein tensor, definedInTermsOf, Riemann curvature tensor via contractions]
  • A. defined
    Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
  • B. partlyDefinedBy chosen
    Indicates that one entity’s nature, role, or characteristics are only partially determined or specified by another entity.
  • C. definedOn
    Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
  • D. endDefinedBy
    Indicates that the termination or boundary of one entity is determined, specified, or constrained by another entity.
  • E. determinedBy
    Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by 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_69a2e7e5c5bc8190a1dc8178218fba40 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2efbed5b88190a45716812eb4cfdf completed Feb. 28, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69a2ede8eac081908dffade6a5e7950b completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.