Triple
T25130792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R∞ |
E629516
|
entity |
| Predicate | appearsInFormula |
P12675
|
FINISHED |
| Object | 1/λ = R∞ (1/n₁² − 1/n₂²) |
—
|
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: 1/λ = R∞ (1/n₁² − 1/n₂²) | Statement: [R∞, appearsInFormula, 1/λ = R∞ (1/n₁² − 1/n₂²)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInFormula Context triple: [R∞, appearsInFormula, 1/λ = R∞ (1/n₁² − 1/n₂²)]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
mathematicallyExpressedBy
chosen
Indicates that something (such as a concept, quantity, or relationship) is represented or captured using a specific mathematical expression or formulation.
-
C.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
D.
isFormulatedUsing
Indicates that something is created, defined, or expressed by means of a specified method, material, or set of components.
-
E.
appearsInFullNameOf
Indicates that one entity (typically a string or term) occurs as a contiguous part within the complete name of 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:28 a.m.