Triple
T10732378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIC Malta |
E253104
|
entity |
| Predicate | domainNameSystemScope |
P14843
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [NIC Malta, domainNameSystemScope, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainNameSystemScope Context triple: [NIC Malta, domainNameSystemScope, national]
-
A.
routingDomainScope
Indicates the specific routing domain or context within which a route, policy, or network configuration is valid or applied.
-
B.
DNS
chosen
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.
-
C.
DNSZone
Indicates a relationship where a set of DNS records is grouped and managed together under a specific domain namespace as a single administrative unit.
-
D.
domainServed
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
E.
recognizedAsDomain
Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7101f35888190b88662372a7d100d |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.