Triple
T37875330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fale |
E944703
|
entity |
| Predicate | hasInternetTLDOfTerritory |
P11776
|
FINISHED |
| Object | .tk |
—
|
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: .tk | Statement: [Fale, hasInternetTLDOfTerritory, .tk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternetTLDOfTerritory Context triple: [Fale, hasInternetTLDOfTerritory, .tk]
-
A.
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).
-
B.
internetTLD
Indicates that one entity is the internet top-level domain (TLD) associated with the other entity.
-
C.
countryCodeTopLevelDomain
chosen
Indicates that a country is associated with a specific top-level internet domain code (ccTLD).
-
D.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
E.
territorialDomain
Indicates that one entity has territorial authority, control, or jurisdiction over a geographic area or domain associated with another entity.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a013d7180d08190b76f64cb430af9e1 |
completed | May 11, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_6a013c77d23c8190bb59e458b506d6e9 |
completed | May 11, 2026, 2:18 a.m. |
Created at: May 3, 2026, 4:19 p.m.