Triple
T272143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diffie–Hellman key exchange |
E5655
|
entity |
| Predicate | hasStep |
P9959
|
FINISHED |
| Object | selection of a large prime modulus |
—
|
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: selection of a large prime modulus | Statement: [Diffie–Hellman key exchange, hasStep, selection of a large prime modulus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStep Context triple: [Diffie–Hellman key exchange, hasStep, selection of a large prime modulus]
-
A.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
B.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
C.
hasCurrent
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
-
D.
hasInitial
Indicates that one entity possesses or is associated with the first letter or starting character of another entity’s name or value.
-
E.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25e69a9248190b9e7959b43223baa |
completed | Feb. 28, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69a25b721180819080d43c43fcbccf87 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e68f0408190bfc851c32d6eebf3 |
completed | Feb. 28, 2026, 3:18 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.