Triple
T19689488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | distance covariance |
E472795
|
entity |
| Predicate | hasNormalizedForm |
P48405
|
FINISHED |
| Object | distance correlation |
—
|
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: distance correlation | Statement: [distance covariance, hasNormalizedForm, distance correlation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNormalizedForm Context triple: [distance covariance, hasNormalizedForm, distance correlation]
-
A.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
B.
usesNormalization
chosen
Indicates that one entity applies or relies on a normalization process or technique in relation to another entity or data.
-
C.
hasNonStandardForm
Indicates that an entity possesses a form, variant, or representation that deviates from the standard, canonical, or commonly accepted form.
-
D.
hasNaturalForm
Indicates that an entity possesses an inherent, unaltered, or naturally occurring form or state.
-
E.
normativeFormUntil
Indicates that a particular normative form or standard applies to something only up to a specified point in time, after which it is no longer in effect.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420f1a0c8190ae59aa0ab3ff2802 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.