Triple
T30194272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7481 |
E767579
|
entity |
| Predicate | definesSecurityServicesFor |
P22776
|
FINISHED |
| Object | Registration Data Access Protocol |
—
|
NE NERFINISHED |
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: Registration Data Access Protocol | Statement: [RFC 7481, definesSecurityServicesFor, Registration Data Access Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSecurityServicesFor Context triple: [RFC 7481, definesSecurityServicesFor, Registration Data Access Protocol]
-
A.
isSecurityFor
Indicates that one entity serves as protection, safeguard, or collateral guaranteeing the obligations, value, or safety of another entity.
-
B.
providesAuthorityFor
Indicates that one entity grants or serves as the basis of authority or permission for another entity to act or make decisions.
-
C.
securityService
chosen
Indicates a relationship where an entity provides or is responsible for protective, safeguarding, or defense-related services for another entity or system.
-
D.
definesService
Indicates that one entity specifies or establishes the service provided or implemented by another entity.
-
E.
supportsUserServices
Indicates that one entity provides the necessary functionality or resources for user-facing services to operate or be delivered.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 29, 2026, 7:29 p.m.