Triple
T8176694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigerian |
E190952
|
entity |
| Predicate | associatedWithInternetTLD |
P248
|
FINISHED |
| Object | .ng |
—
|
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: .ng | Statement: [Nigerian, associatedWithInternetTLD, .ng]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithInternetTLD Context triple: [Nigerian, associatedWithInternetTLD, .ng]
-
A.
internetTLD
chosen
Indicates that one entity is the internet top-level domain (TLD) associated with the other entity.
-
B.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
C.
relatedTLD
Indicates that one top-level domain (TLD) has an association or connection with another TLD, such as similarity, shared purpose, or contextual relevance.
-
D.
hasTopLevelDomain
Indicates that one entity (typically a website, domain name, or internet resource) is associated with a specific top-level domain (such as .com, .org, or .uk).
-
E.
ICANNApproved
Indicates that an entity (such as a domain, registrar, or policy) has been formally reviewed and granted approval by ICANN, the Internet Corporation for Assigned Names and Numbers.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4aba0dd88190828080d0d89612eb |
completed | March 31, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.