Triple
T30152520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resource Public Key Infrastructure |
E766430
|
entity |
| Predicate | allocationsDelegatedTo |
P108451
|
FINISHED |
| Object | Regional Internet Registries |
—
|
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: Regional Internet Registries | Statement: [Resource Public Key Infrastructure, allocationsDelegatedTo, Regional Internet Registries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allocationsDelegatedTo Context triple: [Resource Public Key Infrastructure, allocationsDelegatedTo, Regional Internet Registries]
-
A.
delegatesAllocatedBy
Indicates that one entity has assigned or distributed delegates to another entity.
-
B.
hasDelegations
Indicates that an entity has assigned or transferred certain responsibilities, authority, or tasks to one or more other entities.
-
C.
numberOfDelegations
Indicates the total count of delegation instances associated with a given entity or context.
-
D.
allottedTo
chosen
Indicates that something has been assigned or allocated to a particular entity as its designated recipient or user.
-
E.
hasSmallDelegations
Indicates that an entity maintains or is associated with delegations that are limited in size or scope.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:20 p.m.