Triple
T26441295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HOMFLY-PT homology |
E665095
|
entity |
| Predicate | categorifies |
P160141
|
FINISHED |
| Object | HOMFLY-PT polynomial |
—
|
NE NERFINISHED |
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: HOMFLY-PT polynomial | Statement: [HOMFLY-PT homology, categorifies, HOMFLY-PT polynomial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categorifies Context triple: [HOMFLY-PT homology, categorifies, HOMFLY-PT polynomial]
-
A.
categorifies
chosen
Indicates that one entity provides a higher-level, category-theoretic abstraction or refinement of the structure or behavior of another entity.
-
B.
categorifiedBy
Indicates that something is assigned to or placed within a specific category by another entity.
-
C.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
D.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
categoryDistinguishedFrom
Indicates that one category is explicitly distinguished from another, clarifying that they are separate and should not be confused.
- 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_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_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:58 p.m.