Triple
T26440918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander polynomial |
E665082
|
entity |
| Predicate | computableFrom |
P49064
|
FINISHED |
| Object | Wirtinger presentation of the knot group |
—
|
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: Wirtinger presentation of the knot group | Statement: [Alexander polynomial, computableFrom, Wirtinger presentation of the knot group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computableFrom Context triple: [Alexander polynomial, computableFrom, Wirtinger presentation of the knot group]
-
A.
computabilityRequirement
Indicates that something must be capable of being computed or effectively carried out by an algorithm or computational process.
-
B.
isUsedToCompute
chosen
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
-
C.
computationalClass
Indicates that two entities share the same computational complexity class or that one entity is categorized within a specified computational complexity class.
-
D.
computationInput
Indicates that an entity serves as input data or parameters consumed by a computation or processing activity.
-
E.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
- 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_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 11:58 p.m.