Triple
T29010965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS Service Discovery |
E736563
|
entity |
| Predicate | serviceInstanceNamingFormat |
P2555
|
FINISHED |
| Object | "Instance.Service.Domain" |
—
|
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: "Instance.Service.Domain" | Statement: [DNS Service Discovery, serviceInstanceNamingFormat, "Instance.Service.Domain"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceInstanceNamingFormat Context triple: [DNS Service Discovery, serviceInstanceNamingFormat, "Instance.Service.Domain"]
-
A.
namingStructure
chosen
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
B.
cloudServiceName
Indicates the specific name assigned to a cloud-based service associated with an entity.
-
C.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
D.
registryFormat
Indicates that one entity specifies the data format or schema used for registering another entity in a registry.
-
E.
codenameFormat
Indicates that an entity’s codename follows a specific prescribed format or pattern.
- 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_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 28, 2026, 9:42 a.m.