Triple
T29142132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5702 |
E738665
|
entity |
| Predicate | specifiesUseInRecordType |
P18110
|
FINISHED |
| Object | DNSKEY |
—
|
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: DNSKEY | Statement: [RFC 5702, specifiesUseInRecordType, DNSKEY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesUseInRecordType Context triple: [RFC 5702, specifiesUseInRecordType, DNSKEY]
-
A.
usedInType
chosen
Indicates that something serves as a component, element, or example within a particular type or category.
-
B.
usedWithType
Indicates that something is typically or appropriately used together with items of a specified type.
-
C.
usedInSignatureOf
Indicates that something (such as a type, parameter, or construct) appears as part of the formal signature of a function, method, or similar callable entity.
-
D.
usedToSpecify
Indicates that one entity is employed to define, clarify, or determine the characteristics or identity of another entity.
-
E.
usedInInterface
Indicates that something is employed or incorporated as a component or element within a user interface.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 11:37 a.m.