Triple
T736631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minkowski sum |
E14947
|
entity |
| Predicate | preservesBoundedness |
P4235
|
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: [Minkowski sum, preservesBoundedness, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservesBoundedness Context triple: [Minkowski sum, preservesBoundedness, true]
-
A.
preservesFeature
Indicates that one entity maintains or keeps intact a particular feature, property, or characteristic of another entity during some process or interaction.
-
B.
isUpperBoundFor
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
-
C.
invariantUnder
chosen
Indicates that a property, structure, or quantity remains unchanged when a specified transformation or operation is applied.
-
D.
dimensionBoundType
Indicates the type or nature of the constraint that bounds a given dimension in a relationship.
-
E.
convergenceProperty
Indicates that one entity has a convergence-related characteristic or behavior with respect to another entity, such as approaching a limit or stabilizing under repeated application.
- F. None of above.
Provenance (3 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fc734c81908fbd36386d5746d6 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.