Triple
T32747380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst Hellinger |
E837389
|
entity |
| Predicate | hasNotableMetricNamedAfter |
P120681
|
FINISHED |
| Object | Hellinger distance |
—
|
NE NERFINISHED |
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: Hellinger distance | Statement: [Ernst Hellinger, hasNotableMetricNamedAfter, Hellinger distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMetricNamedAfter Context triple: [Ernst Hellinger, hasNotableMetricNamedAfter, Hellinger distance]
-
A.
hasNotableMetric
Indicates that an entity is associated with a specific metric or measurement that is considered significant or noteworthy in its context.
-
B.
hasMeasurementNamedAfter
chosen
Indicates that a measurement unit or scale is named in honor of a particular entity.
-
C.
hasNotablePropertyNamedAfter
Indicates that an entity possesses a notable property or attribute that is named in honor of, or derived from, another entity.
-
D.
hasAssociatedMetric
Indicates that an entity is linked to a specific metric used to quantify, evaluate, or monitor some aspect of that entity.
-
E.
isNotableNameOf
Indicates that a name is widely recognized or distinguished as a significant identifier for the referenced 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0143a4ab3c8190a240b0facfe130a9 |
completed | May 11, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_6a01426b2d4481908654bfa4a02c457d |
completed | May 11, 2026, 2:43 a.m. |
Created at: May 1, 2026, 1:12 a.m.