Triple
T26441329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HOMFLY-PT homology |
E665095
|
entity |
| Predicate | baseRing |
P66253
|
FINISHED |
| Object | typically defined over Q or C |
—
|
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: typically defined over Q or C | Statement: [HOMFLY-PT homology, baseRing, typically defined over Q or C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseRing Context triple: [HOMFLY-PT homology, baseRing, typically defined over Q or C]
-
A.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
-
B.
ringType
chosen
Indicates the specific kind or category of ring associated with an entity or relationship.
-
C.
ringsBy
Indicates that one entity creates or designs rings that are associated with, produced by, or attributed to another entity.
-
D.
ringOrigin
Indicates the source or starting point from which a ring (such as a circular structure, feature, or formation) arises or is generated.
-
E.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
- 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_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:58 p.m.