Triple
T338486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4252 |
E6780
|
entity |
| Predicate | definesAuthenticationMethod |
P8684
|
FINISHED |
| Object | publickey |
—
|
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: publickey | Statement: [RFC 4252, definesAuthenticationMethod, publickey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAuthenticationMethod Context triple: [RFC 4252, definesAuthenticationMethod, publickey]
-
A.
hasProofMethod
Indicates that there exists a specific method or technique used to establish or demonstrate the validity of something (such as a statement, claim, or theorem).
-
B.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
C.
definesMechanism
chosen
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
-
D.
credentialType
Indicates the specific kind or category of credential associated with an entity or relationship.
-
E.
confirmationMethod
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae3a27c81909fc7deb600125fb1 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.