Triple
T8210138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FFDHE groups |
E191792
|
entity |
| Predicate | groupStructure |
P81509
|
FINISHED |
| Object | multiplicative group modulo a prime |
—
|
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: multiplicative group modulo a prime | Statement: [FFDHE groups, groupStructure, multiplicative group modulo a prime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupStructure Context triple: [FFDHE groups, groupStructure, multiplicative group modulo a prime]
-
A.
officeHierarchy
Indicates a reporting or supervisory relationship between positions within an office, defining who is above or below whom in the organizational chain of command.
-
B.
workStructure
Indicates how work is organized, arranged, or structured within or between entities.
-
C.
divisionOrStructure
Indicates a relationship where one entity is an internal division, department, or structural subunit that is organizationally contained within another entity.
-
D.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
E.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dd881c8190adcbeb2f33d3295c |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:44 p.m.