Triple
T8746296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .nf |
E207835
|
entity |
| Predicate | hasSecondLevelDomain |
P14842
|
FINISHED |
| Object | .com.nf |
—
|
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.nf | Statement: [.nf, hasSecondLevelDomain, .com.nf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondLevelDomain Context triple: [.nf, hasSecondLevelDomain, .com.nf]
-
A.
secondLevelDomain
chosen
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.
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).
-
C.
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.
-
D.
hasSubdomain
Indicates that one domain is a subordinate or nested part of another domain within a hierarchical naming structure.
-
E.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d75e7c88190a9e78fadb979e1b6 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.