Triple
T36151668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INFORMS Optimization Society Khachiyan Prize |
E1045600
|
entity |
| Predicate | hasNamesakeKnownFor |
P111120
|
FINISHED |
| Object | ellipsoid algorithm in linear programming |
—
|
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: ellipsoid algorithm in linear programming | Statement: [INFORMS Optimization Society Khachiyan Prize, hasNamesakeKnownFor, ellipsoid algorithm in linear programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamesakeKnownFor Context triple: [INFORMS Optimization Society Khachiyan Prize, hasNamesakeKnownFor, ellipsoid algorithm in linear programming]
-
A.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
-
B.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
C.
namedForNotablePersonFrom
Indicates that one entity is named in honor of a notable person who originates from another specified place or group.
-
D.
referentKnownFor
chosen
Indicates that the referent is widely recognized or notable for a particular activity, role, achievement, or characteristic.
-
E.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4:08 p.m.