Triple
T22328889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolbeault cohomology class |
E551971
|
entity |
| Predicate | gradedBy |
P147761
|
FINISHED |
| Object | bidegree (p,q) |
—
|
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: bidegree (p,q) | Statement: [Dolbeault cohomology class, gradedBy, bidegree (p,q)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradedBy Context triple: [Dolbeault cohomology class, gradedBy, bidegree (p,q)]
-
A.
grading
Indicates that one entity is evaluating, scoring, or assigning a quality level to another entity based on specific criteria.
-
B.
isGraded
Indicates that an entity has been evaluated and assigned a grade or score, typically by an assessor or grading process.
-
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.
gradeIn
Indicates that an entity has a particular grade or score within a specified course, assignment, or evaluation context.
-
E.
gradeWithin
Indicates that one value’s grade or level falls within a specified range or interval relative to another.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1576ab52c819087563cd778d6bc5e |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.