Triple
T310346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kullback–Leibler divergence |
E6392
|
entity |
| Predicate | satisfiesTriangleInequality |
P10672
|
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, satisfiesTriangleInequality, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satisfiesTriangleInequality Context triple: [Kullback–Leibler divergence, satisfiesTriangleInequality, false]
-
A.
hasTriangle
Indicates that an entity possesses, contains, or is associated with a triangle.
-
B.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
-
C.
isQuadrangleOf
Indicates that one entity is a four-sided polygon (quadrilateral) that has the other entity as its defining instance or member.
-
D.
isConcaveIn
Indicates that a function or relation curves inward (is concave) with respect to a specified variable or argument, so that any line segment between two points on its graph lies below or on the graph.
-
E.
perpendicularTo
Indicates that one entity is oriented at a right angle (90 degrees) to another entity.
- 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.