Triple
T4461560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigner surmise |
E98265
|
entity |
| Predicate | GOEFormula |
P2310
|
FINISHED |
| Object | P(s) = (π/2) s exp(-π s^2 / 4) |
—
|
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: P(s) = (π/2) s exp(-π s^2 / 4) | Statement: [Wigner surmise, GOEFormula, P(s) = (π/2) s exp(-π s^2 / 4)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GOEFormula Context triple: [Wigner surmise, GOEFormula, P(s) = (π/2) s exp(-π s^2 / 4)]
-
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.
recitesFormula
Indicates that one entity verbally or mentally repeats a specific formula, such as a set phrase, equation, or ritual wording, typically from memory.
-
D.
mathematicallyExpressedBy
Indicates that something (such as a concept, quantity, or relationship) is represented or captured using a specific mathematical expression or formulation.
-
E.
generalizedForm
Indicates that one entity is a more abstract, generalized version or broader form 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35674f718819089388c3924dd1414 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:34 p.m.