Triple
T17549858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wirtinger presentation of knot groups |
E427429
|
entity |
| Predicate | isAlgorithmic |
P79475
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wirtinger presentation of knot groups, isAlgorithmic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlgorithmic Context triple: [Wirtinger presentation of knot groups, isAlgorithmic, true]
-
A.
algorithmicProperty
chosen
Indicates that a subject possesses a specific characteristic, behavior, or quality defined in terms of an algorithm or computational procedure.
-
B.
relatedAlgorithm
Indicates that one algorithm has a meaningful connection or association with another algorithm, such as similarity, dependency, or complementary function.
-
C.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
D.
supportsOptimizationAlgorithm
Indicates that one entity is capable of running, integrating, or being compatible with a specified optimization algorithm.
-
E.
hasRankingAlgorithm
Indicates that an entity uses or is associated with a specific algorithm for ranking or ordering items.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45463ddf88190a2c29f3246adcb6e |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.