Triple
T9843735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cauchy distribution |
E239287
|
entity |
| Predicate | hasMedianAbsoluteDeviation |
P49861
|
FINISHED |
| Object | γ |
—
|
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: γ | Statement: [Cauchy distribution, hasMedianAbsoluteDeviation, γ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedianAbsoluteDeviation Context triple: [Cauchy distribution, hasMedianAbsoluteDeviation, γ]
-
A.
medianEquals
Indicates that the median value of a given set or sequence is equal to a specified value.
-
B.
medidaCentral
Indicates a relationship where something functions as a central or primary measure used to summarize or represent a set of values.
-
C.
hasMAD
chosen
Indicates that an entity possesses or is associated with a specific MAD (e.g., a minimum acceptable distance, mean absolute deviation, or similarly defined MAD-related measure).
-
D.
hasStandardDeviationSymbol
Indicates that a given notation, variable, or symbol is used to represent the standard deviation in a statistical context.
-
E.
hasMedianUse
Indicates that something is associated with a typical or middle level of use within a given range or distribution of usage.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35c8e348190aa090c71bf6f30eb |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.