Triple
T30408314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7484 |
E773538
|
entity |
| Predicate | registryDependency |
P170764
|
FINISHED |
| Object | IANA RDAP Bootstrap 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: IANA RDAP Bootstrap Registries | Statement: [RFC 7484, registryDependency, IANA RDAP Bootstrap Registries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registryDependency Context triple: [RFC 7484, registryDependency, IANA RDAP Bootstrap Registries]
-
A.
kernelDependsOn
Indicates that one kernel or core software component requires another kernel or component to be present or available in order to function correctly.
-
B.
registryType
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
-
C.
relatedRegistry
Indicates that one registry has an association or linkage to another registry.
-
D.
registryURL
Indicates the web address where an entity’s official registration information is stored or can be accessed.
-
E.
registryKey
Indicates a relationship where a software component or process creates, modifies, or references a specific key within a system’s registry.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:04 p.m.