Triple
T38438092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurwitz group |
E904003
|
entity |
| Predicate | lowerBoundOnGenus |
P174573
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Hurwitz group, lowerBoundOnGenus, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerBoundOnGenus Context triple: [Hurwitz group, lowerBoundOnGenus, 2]
-
A.
HurwitzBoundForGenus3
Indicates that the relationship or action concerns the application or satisfaction of the Hurwitz bound on the order of the automorphism group for algebraic curves of genus 3.
-
B.
forSurfaceOfGenus
Indicates that one entity is the surface associated with or belonging to a particular genus.
-
C.
lowerBoundGrowth
Indicates that one quantity grows at least as fast as another, establishing a minimum rate or bound on its growth relative to that reference.
-
D.
lowerBoundProperty
chosen
Indicates that one entity serves as the minimum or lowest permissible value, limit, or constraint for another entity or quantity.
-
E.
minimumDegree
Indicates that the relationship specifies the smallest number of connections or edges incident to any entity within a given structure or set.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.