Triple
T30350801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .info |
E771982
|
entity |
| Predicate | managedUnderPolicy |
P42489
|
FINISHED |
| Object | ICANN gTLD policies |
—
|
NE NERFINISHED |
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: ICANN gTLD policies | Statement: [.info, managedUnderPolicy, ICANN gTLD policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedUnderPolicy Context triple: [.info, managedUnderPolicy, ICANN gTLD policies]
-
A.
establishedUnderPolicy
Indicates that something was created, founded, or formally set up as a result of, or in accordance with, a specific policy.
-
B.
negotiatedUnderPolicy
Indicates that an agreement or arrangement was reached through a negotiation process conducted in accordance with a specific policy or set of policy rules.
-
C.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
D.
managedUnderContractWith
Indicates that one entity is responsible for managing another entity or service based on the terms of a formal contract with a specified party.
-
E.
targetedByPolicy
chosen
Indicates that an entity is the intended subject or focus of a specific policy’s rules, actions, or effects.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 7:56 p.m.