Triple
T11215032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dehn twist |
E265413
|
entity |
| Predicate | algebraicEffect |
P97880
|
FINISHED |
| Object | acts on fundamental group of the surface |
—
|
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: acts on fundamental group of the surface | Statement: [Dehn twist, algebraicEffect, acts on fundamental group of the surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: algebraicEffect Context triple: [Dehn twist, algebraicEffect, acts on fundamental group of the surface]
-
A.
sideEffect
Indicates that one entity is an unintended or secondary effect resulting from the use or occurrence of another entity.
-
B.
usesEffectType
Indicates that an entity employs or is associated with a particular type or category of effect in its operation or behavior.
-
C.
enqueueMethodEffect
Indicates that an operation adds a method (or its invocation) to a queue to be executed later.
-
D.
findsEffect
Indicates that one entity discovers, identifies, or determines the effect or outcome produced by another entity.
-
E.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8e8eef48190932a85784ce15c86 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.