Triple
T480310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .ng |
E9152
|
entity |
| Predicate | exampleSecondLevelDomain |
P14826
|
FINISHED |
| Object | .com.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: .com.ng | Statement: [.ng, exampleSecondLevelDomain, .com.ng]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleSecondLevelDomain Context triple: [.ng, exampleSecondLevelDomain, .com.ng]
-
A.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
-
B.
exampleZoneName
Indicates that an entity is associated with a zone identified by a specific example or placeholder name.
-
C.
internetTLD
Indicates that one entity is the internet top-level domain (TLD) associated with the other entity.
-
D.
emailAddressDomain
Indicates that one entity is the domain portion (e.g., "example.com") of another entity’s email address.
-
E.
primaryDomain
Indicates that one domain is the main or most important domain associated with an entity, as opposed to any secondary or alternate domains.
- F. None of above. chosen
Provenance (4 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f057c4ac819080cf43ffaa56c350 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf1d5848190a7da27e2fddc136f |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef4030608190b39852b347a505ca |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.