Triple
T32747313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jensen–Shannon divergence |
E837388
|
entity |
| Predicate | entropyForm |
P175060
|
FINISHED |
| Object | JSD(P‖Q) = H(M) − 1/2 H(P) − 1/2 H(Q) |
—
|
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: JSD(P‖Q) = H(M) − 1/2 H(P) − 1/2 H(Q) | Statement: [Jensen–Shannon divergence, entropyForm, JSD(P‖Q) = H(M) − 1/2 H(P) − 1/2 H(Q)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entropyForm Context triple: [Jensen–Shannon divergence, entropyForm, JSD(P‖Q) = H(M) − 1/2 H(P) − 1/2 H(Q)]
-
A.
potentialForm
Indicates that an action is expressed in its potential form, meaning the subject has the ability or possibility to perform that action.
-
B.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
-
C.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
D.
encodingForm
Indicates the specific format or scheme used to encode information or data in a representation or communication.
-
E.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
- 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.