Triple
T8723842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6605 |
E207080
|
entity |
| Predicate | definesRRTypeUsage |
P56536
|
FINISHED |
| Object | DNSKEY |
—
|
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: DNSKEY | Statement: [RFC 6605, definesRRTypeUsage, DNSKEY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesRRTypeUsage Context triple: [RFC 6605, definesRRTypeUsage, DNSKEY]
-
A.
definesType
chosen
Indicates that one entity specifies or establishes the type or classification of another entity.
-
B.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
registerType
Indicates that an entity is classified or recorded under a specific type or category within a registration system.
-
E.
usesRoutingType
Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d0791208190b043332247372d7b |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.