Triple
T1405496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .ch |
E31681
|
entity |
| Predicate | zoneFile |
P12950
|
FINISHED |
| Object | publicly available |
—
|
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: publicly available | Statement: [.ch, zoneFile, publicly available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneFile Context triple: [.ch, zoneFile, publicly available]
-
A.
ianaZoneFile
chosen
Indicates that an entity is associated with, defined by, or described in a specific IANA DNS zone file.
-
B.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
C.
DNS
Indicates a relationship where one entity serves as or is associated with a Domain Name System (DNS) configuration or service for another entity, enabling the translation of domain names to network addresses.
-
D.
exampleZoneName
Indicates that an entity is associated with a zone identified by a specific example or placeholder name.
-
E.
zoneManagedFrom
Indicates that a particular zone or area is administered, controlled, or overseen from a specified location or managing 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bc55a08190a4dfe13a5378aff3 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.