Triple
T30350803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .info |
E771982
|
entity |
| Predicate | supportsThirdLevelDomains |
P207232
|
FINISHED |
| Object | yes via 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: yes via registrants | Statement: [.info, supportsThirdLevelDomains, yes via registrants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsThirdLevelDomains Context triple: [.info, supportsThirdLevelDomains, yes via registrants]
-
A.
secondLevelDomain
Indicates that one entity is the second-level domain associated with, or extracted from, another entity such as a full domain name or URL.
-
B.
supportsSecondLevelRegistrations
Indicates that an entity allows or enables second-level domain registrations directly under it.
-
C.
supportsCustomDomain
Indicates that an entity provides the capability to use or configure a custom domain name instead of a default or system-assigned domain.
-
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.
exampleSecondLevelDomain
Indicates that one entity is an example of a second-level domain (the part of a domain name directly below a top-level domain) associated with another entity.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 7:56 p.m.