Triple
T8210153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FFDHE groups |
E191792
|
entity |
| Predicate | recommendedMinimumSize |
P81510
|
FINISHED |
| Object | 2048 bits |
—
|
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: 2048 bits | Statement: [FFDHE groups, recommendedMinimumSize, 2048 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedMinimumSize Context triple: [FFDHE groups, recommendedMinimumSize, 2048 bits]
-
A.
minimumUnitSize
Indicates that there is a smallest allowable or defined size or quantity for the unit involved in the relationship.
-
B.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
-
C.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
D.
headerMinimumSize
Indicates that there is a constraint specifying the smallest allowable size for a header.
-
E.
minimumFrameSize
Indicates the smallest allowable or supported size of a frame in the given context or system.
- 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.