Triple
T36468608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenchel–Nielsen coordinates |
E898483
|
entity |
| Predicate | numberOfTwistParameters |
P133198
|
FINISHED |
| Object | 3g - 3 + n |
—
|
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: 3g - 3 + n | Statement: [Fenchel–Nielsen coordinates, numberOfTwistParameters, 3g - 3 + n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfTwistParameters Context triple: [Fenchel–Nielsen coordinates, numberOfTwistParameters, 3g - 3 + n]
-
A.
twistCount
chosen
Indicates the number of twists or rotational turns applied or present in the relationship between the related entities.
-
B.
twistType
Indicates the specific manner or category of twisting applied in a relationship or action between entities.
-
C.
twistOffAngle
Indicates the angular amount or orientation by which something is twisted off from its original or reference position.
-
D.
hasTwist
Indicates that an entity (such as a story, object, or feature) includes an unexpected change, reversal, or surprising element relative to what was previously established or anticipated.
-
E.
hasTwistType
Indicates that one entity is associated with a specific kind or category of twist applied to it.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.