Triple
T16262605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian domain name policy |
E394790
|
entity |
| Predicate | allowsRegistrationBy |
P111930
|
FINISHED |
| Object | organizations in Norway |
—
|
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: organizations in Norway | Statement: [Norwegian domain name policy, allowsRegistrationBy, organizations in Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsRegistrationBy Context triple: [Norwegian domain name policy, allowsRegistrationBy, organizations in Norway]
-
A.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
B.
allowsRegulationOf
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
C.
allowsAffiliationOf
chosen
Indicates that one entity grants permission or enables another entity to establish or hold an affiliation with it.
-
D.
registrationMode
Indicates the method or process by which something is registered or enrolled.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c5583c8190901e892238cf8dbd |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.