Triple
T25097469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laplace distribution |
E628628
|
entity |
| Predicate | peakShape |
P35194
|
FINISHED |
| Object | sharper peak at mean than normal distribution |
—
|
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: sharper peak at mean than normal distribution | Statement: [Laplace distribution, peakShape, sharper peak at mean than normal distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakShape Context triple: [Laplace distribution, peakShape, sharper peak at mean than normal distribution]
-
A.
peakType
chosen
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
B.
peakBroadness
Indicates how wide or spread out a peak is across its range, rather than how tall or high it is.
-
C.
peakFunction
Indicates that a function reaches a maximum (peak) value at a specific point or over a given interval.
-
D.
peakSize
Indicates the magnitude or height of a peak within a given signal, distribution, or dataset.
-
E.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464ba4e148190a8169ac91b2f85b6 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:25 a.m.