Triple
T24621006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersenne’s laws of vibrating strings |
E609411
|
entity |
| Predicate | combinedFormula |
P2310
|
FINISHED |
| Object | f = (1 / 2L) · √(T / μ) |
—
|
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: f = (1 / 2L) · √(T / μ) | Statement: [Mersenne’s laws of vibrating strings, combinedFormula, f = (1 / 2L) · √(T / μ)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinedFormula Context triple: [Mersenne’s laws of vibrating strings, combinedFormula, f = (1 / 2L) · √(T / μ)]
-
A.
formulaUsed
Indicates that a particular formula is employed or applied in performing a calculation, derivation, or reasoning step.
-
B.
keyFormula
chosen
Indicates that a formula serves as the primary or defining expression associated with an entity or relationship.
-
C.
combinedFunction
Indicates that multiple functions or operations are brought together and applied as a single, unified function or process.
-
D.
recitesFormula
Indicates that one entity verbally or mentally repeats a specific formula, such as a set phrase, equation, or ritual wording, typically from memory.
-
E.
formulaType
Indicates the specific kind or category of formula associated with an entity or expression.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.