Triple
T33578949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobian variety |
E860099
|
entity |
| Predicate | groupLaw |
P176910
|
FINISHED |
| Object | addition of divisor classes |
—
|
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: addition of divisor classes | Statement: [Jacobian variety, groupLaw, addition of divisor classes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupLaw Context triple: [Jacobian variety, groupLaw, addition of divisor classes]
-
A.
groupLawIs
Indicates that a specified binary operation on a set satisfies the axioms of a group (closure, associativity, identity, and inverses), thereby forming a group structure.
-
B.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
C.
groupWithin
Indicates that one group is contained or nested as a subgroup within another, larger group.
-
D.
groupTogether
Indicates that multiple entities are treated or arranged as a single collective unit or set.
-
E.
incorporatedGroup
Indicates that one entity is a formally constituted group or organization that has been legally incorporated.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:40 a.m.