Triple
T1696084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7919 |
E36660
|
entity |
| Predicate | definesGroup |
P16559
|
FINISHED |
| Object | ffdhe2048 |
—
|
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: ffdhe2048 | Statement: [RFC 7919, definesGroup, ffdhe2048]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesGroup Context triple: [RFC 7919, definesGroup, ffdhe2048]
-
A.
labelGroup
chosen
Indicates that an entity is assigned to or associated with a particular group label used for categorization or organization.
-
B.
interactsWithGroup
Indicates that an entity engages in actions or exchanges with a collective group of other entities.
-
C.
positionGroup
Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
-
D.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
E.
definesBranch
Indicates that one entity specifies or establishes a particular branch or subdivision of another entity.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.