Triple
T9932860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ccTLD registry |
E192686
|
entity |
| Predicate | maySetPolicyOn |
P5524
|
FINISHED |
| Object | eligibility requirements for domain registrants |
—
|
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: eligibility requirements for domain registrants | Statement: [ccTLD registry, maySetPolicyOn, eligibility requirements for domain registrants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySetPolicyOn Context triple: [ccTLD registry, maySetPolicyOn, eligibility requirements for domain registrants]
-
A.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
B.
canSet
chosen
Indicates that one entity has the ability or permission to assign, configure, or change a property, value, or state of another entity.
-
C.
mayRuleOver
Indicates that one entity has the potential or permission to exercise authority or governance over another entity.
-
D.
eraPolicy
Indicates that a specific policy was in effect during a particular historical or temporal era.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b7897081909b28189aa57af250 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.