Triple
T16262621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian domain name policy |
E394790
|
entity |
| Predicate | requiresRegistrarAgreement |
P87597
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Norwegian domain name policy, requiresRegistrarAgreement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresRegistrarAgreement Context triple: [Norwegian domain name policy, requiresRegistrarAgreement, yes]
-
A.
requiresAgreementWith
chosen
Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified entity.
-
B.
hasAgreementSystem
Indicates that there exists a specific grammatical agreement system (e.g., for features like number, gender, or person) associated with the given entity.
-
C.
canEnterIntoAgreementsWith
Indicates that one entity has the legal or formal capacity to make binding agreements or contracts with another entity.
-
D.
establishedByAgreementSignedIn
Indicates that something was formally created or instituted as a result of an agreement that was signed at a specific time or place.
-
E.
registrationRequirement
Indicates that an entity is obligated to formally register with a specified authority, system, or registry under certain conditions.
- 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.