Triple
T310345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kullback–Leibler divergence |
E6392
|
entity |
| Predicate | isSymmetric |
P10671
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Kullback–Leibler divergence, isSymmetric, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSymmetric Context triple: [Kullback–Leibler divergence, isSymmetric, false]
-
A.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
-
B.
invariantUnder
Indicates that a property, structure, or quantity remains unchanged when a specified transformation or operation is applied.
-
C.
isStable
Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
-
D.
isProportionalTo
Indicates that one quantity varies in constant ratio to another, so when one changes, the other changes by a fixed multiplicative factor.
-
E.
hasCurvatureInvariant
Indicates that one entity possesses a specific curvature-related invariant property or value associated with its geometric or mathematical structure.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea07e3bc8190bae593b3264de211 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.