Triple
T25097492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | double exponential distribution |
E628629
|
entity |
| Predicate | hasStandardDeviation |
P164777
|
FINISHED |
| Object | √2 b |
—
|
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: √2 b | Statement: [double exponential distribution, hasStandardDeviation, √2 b]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardDeviation Context triple: [double exponential distribution, hasStandardDeviation, √2 b]
-
A.
hasStandardDeviationSymbol
Indicates that a given notation, variable, or symbol is used to represent the standard deviation in a statistical context.
-
B.
hasVariance
Indicates that there is a measurable degree of variability or dispersion in the values or outcomes associated with the related entities.
-
C.
hasStatisticalFunctions
Indicates that one entity provides or supports statistical operations or capabilities for another entity.
-
D.
hasStatistics
Indicates that an entity is associated with one or more statistical measures, records, or summaries describing its quantitative properties or performance.
-
E.
hasStationaryMean
Indicates that the associated process or variable has a mean value that does not change over time.
- F. None of above. chosen
Provenance (4 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 18, 2026, 6:25 a.m.