Triple
T32747325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jensen–Shannon divergence |
E837388
|
entity |
| Predicate | isFdivergence |
P175061
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Jensen–Shannon divergence, isFdivergence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFdivergence Context triple: [Jensen–Shannon divergence, isFdivergence, true]
-
A.
isDivergenceFreeIn
Indicates that a field or quantity has zero divergence (i.e., no net source or sink) within a specified region or domain.
-
B.
hasDivergence
Indicates that there is a difference, deviation, or separation between two otherwise related entities, states, or paths.
-
C.
hasCurvatureDivergence
Indicates that one entity exhibits a difference or variation in curvature relative to another entity or reference.
-
D.
isDifferenceOf
Indicates that one quantity or entity represents the result obtained by subtracting one specified quantity or entity from another.
-
E.
isDifferential
Indicates that one quantity represents the infinitesimal change or derivative of another with respect to a given variable.
- 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.