Triple
T29010966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS Service Discovery |
E736563
|
entity |
| Predicate | usesServiceTypeSyntax |
P180868
|
FINISHED |
| Object | "_service._proto" |
—
|
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: "_service._proto" | Statement: [DNS Service Discovery, usesServiceTypeSyntax, "_service._proto"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesServiceTypeSyntax Context triple: [DNS Service Discovery, usesServiceTypeSyntax, "_service._proto"]
-
A.
usesServiceDesignation
Indicates that one entity adopts or applies a particular service designation associated with another entity or offering.
-
B.
usedWithType
Indicates that something is typically or appropriately used together with items of a specified type.
-
C.
usedByServiceTo
Indicates that something (such as a resource, component, or feature) is utilized or consumed by a particular service to perform its functions.
-
D.
usedForService
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
-
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. 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: April 28, 2026, 9:42 a.m.