Triple
T23564514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .sj |
E579332
|
entity |
| Predicate | internetRegistryPolicy |
P4800
|
FINISHED |
| Object | Norwegian national domain policy |
—
|
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: Norwegian national domain policy | Statement: [.sj, internetRegistryPolicy, Norwegian national domain policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internetRegistryPolicy Context triple: [.sj, internetRegistryPolicy, Norwegian national domain policy]
-
A.
integrationPolicy
Indicates the rules or strategy governing how separate components, systems, or processes are combined and made to work together.
-
B.
publicPolicy
Indicates that an entity is a government or institutional rule, principle, or course of action intended to address public issues or guide societal outcomes.
-
C.
regulatoryDomain
chosen
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
D.
dnsPolicy
Indicates the DNS resolution strategy or configuration policy that governs how domain names are resolved for the associated entity.
-
E.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6b04cc81909385e485b8bdd54b |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:33 p.m.