Triple
T36093855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slater’s condition |
E1044001
|
entity |
| Predicate | isSufficientFor |
P94877
|
FINISHED |
| Object | strong duality in convex programs |
—
|
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: strong duality in convex programs | Statement: [Slater’s condition, isSufficientFor, strong duality in convex programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSufficientFor Context triple: [Slater’s condition, isSufficientFor, strong duality in convex programs]
-
A.
sufficientConditionFor
chosen
Indicates that the truth or occurrence of one entity guarantees or ensures the truth or occurrence of another entity.
-
B.
notSufficientFor
Indicates that the presence or occurrence of one condition does not by itself guarantee or bring about the other condition.
-
C.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
D.
givesNecessaryAndSufficientConditionFor
Indicates that one entity provides a condition or set of conditions that are both required and alone adequate for another entity, concept, or statement to hold or be true.
-
E.
isApprovedFor
Indicates that one entity has been officially authorized, accepted, or permitted for use, access, or association with another entity.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.