Triple
T4461559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigner surmise |
E98265
|
entity |
| Predicate | meanSpacingCondition |
P52973
|
FINISHED |
| Object | ∫₀^∞ s P(s) ds = 1 |
—
|
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: ∫₀^∞ s P(s) ds = 1 | Statement: [Wigner surmise, meanSpacingCondition, ∫₀^∞ s P(s) ds = 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meanSpacingCondition Context triple: [Wigner surmise, meanSpacingCondition, ∫₀^∞ s P(s) ds = 1]
-
A.
gapBetween
Indicates the spatial or temporal distance or separation that exists between two entities.
-
B.
equalityCondition
chosen
Indicates that two values, expressions, or attributes must be exactly the same for the condition to be satisfied.
-
C.
clusterDensity
Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
-
D.
metBetween
Indicates that two or more entities had an in-person or virtual meeting or encounter with each other during a specified time or context.
-
E.
hasMeanDensity
Indicates that one entity possesses a specified average mass per unit volume (mean density).
- 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.