Triple
T29010949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS Service Discovery |
E736563
|
entity |
| Predicate | usesRecordType |
P2554
|
FINISHED |
| Object | DNS SRV record |
—
|
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: DNS SRV record | Statement: [DNS Service Discovery, usesRecordType, DNS SRV record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRecordType Context triple: [DNS Service Discovery, usesRecordType, DNS SRV record]
-
A.
usesRecordCode
Indicates that one entity employs or references a specific record code associated with another entity or resource.
-
B.
hasRecordType
chosen
Indicates that an entity is associated with or classified under a specific type or category of record.
-
C.
recordsType
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
-
D.
isRecord
Indicates that one entity functions as an official or authoritative record of another entity or of some information.
-
E.
trackRecordUsedFor
Indicates that a track record is utilized as a basis or input for some subsequent decision, evaluation, or process.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 9:42 a.m.