Triple
T32747327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jensen–Shannon divergence |
E837388
|
entity |
| Predicate | metricName |
P175063
|
FINISHED |
| Object | Jensen–Shannon 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: Jensen–Shannon distance | Statement: [Jensen–Shannon divergence, metricName, Jensen–Shannon distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricName Context triple: [Jensen–Shannon divergence, metricName, Jensen–Shannon distance]
-
A.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
B.
metricComponent
Indicates a relationship where one element functions as a component or constituent part of a larger metric.
-
C.
definesMetric
Indicates that one entity specifies or establishes a metric (a standard of measurement or evaluation) that is applied to or used by another entity.
-
D.
metricForm
Indicates that one entity is expressed or represented in a particular metric form or measurement format relative to another.
-
E.
metricSignature
Indicates that one mathematical object (typically a metric or space) has a specific signature characterizing the signs and multiplicities of its metric components.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:12 a.m.