Triple
T30152521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resource Public Key Infrastructure |
E766430
|
entity |
| Predicate | RIR |
P168489
|
FINISHED |
| Object | AFRINIC |
—
|
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: AFRINIC | Statement: [Resource Public Key Infrastructure, RIR, AFRINIC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RIR Context triple: [Resource Public Key Infrastructure, RIR, AFRINIC]
-
A.
RIC
Indicates a relationship in which one entity is responsible for insuring or providing insurance coverage to another entity or asset.
-
B.
supportsRDAP
Indicates that one entity provides or is compatible with RDAP (Registration Data Access Protocol) functionality for another entity.
-
C.
rfStandard
Indicates a relationship where something conforms to, follows, or is defined by a particular radio frequency (RF) standard or specification.
-
D.
rimRepresents
Indicates that one entity serves as a representation, model, or stand-in for another entity within a specific context or system.
-
E.
registeredWithIANA
Indicates that an entity is officially recorded and recognized by the Internet Assigned Numbers Authority (IANA) in its registries.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4df5081908d1431e3a1a1fb0e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:20 p.m.