Triple
T26254684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khovanov homology |
E656685
|
entity |
| Predicate | hasGrading |
P164828
|
FINISHED |
| Object | homological grading |
—
|
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: homological grading | Statement: [Khovanov homology, hasGrading, homological grading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrading Context triple: [Khovanov homology, hasGrading, homological grading]
-
A.
isGraded
Indicates that an entity has been evaluated and assigned a grade or score, typically by an assessor or grading process.
-
B.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
C.
isGradedBy
Indicates that an entity (such as an assignment, exam, or work) is evaluated and assigned a grade by another entity (such as a person, system, or organization).
-
D.
hasGradeStatus
Indicates that an entity holds a particular grade-related status or standing within an evaluation or grading system.
-
E.
hasGradingBody
Indicates that one entity serves as the official organization or authority responsible for grading, evaluating, or assessing 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 26, 2026, 9:08 p.m.