Triple
T26441302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HOMFLY-PT homology |
E665095
|
entity |
| Predicate | gradingTypes |
P160758
|
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: [HOMFLY-PT homology, gradingTypes, homological grading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradingTypes Context triple: [HOMFLY-PT homology, gradingTypes, homological grading]
-
A.
grading
Indicates that one entity is evaluating, scoring, or assigning a quality level to another entity based on specific criteria.
-
B.
gradeHierarchy
Indicates a hierarchical relationship between grades or levels, where one grade is ranked above or below another in an ordered structure.
-
C.
hasGradeType
Indicates that an entity is associated with a particular category or type of grade (e.g., letter grade, pass/fail, percentage).
-
D.
gradingRole
Indicates that an entity has the role or responsibility of evaluating, scoring, or grading another entity’s work, performance, or output.
-
E.
gradeCategory
Indicates the classification of a grade into a broader category or level (such as letter grade, performance band, or pass/fail group).
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6121bf448819088a5516943658eff |
completed | May 2, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 26, 2026, 11:58 p.m.