Triple
T29092997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFNIC |
E734909
|
entity |
| Predicate | managesTLD |
P91208
|
FINISHED |
| Object | .fr |
—
|
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: .fr | Statement: [AFNIC, managesTLD, .fr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesTLD Context triple: [AFNIC, managesTLD, .fr]
-
A.
managesTopLevelDomain
chosen
Indicates that one entity has administrative authority over and is responsible for operating and maintaining a specific top-level domain on the internet.
-
B.
ccTLDManager
Indicates that an entity is responsible for administering and managing a specific country-code top-level domain (ccTLD) on behalf of a country or territory.
-
C.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
D.
ICANNRootZoneManagedBy
Indicates that the management and administrative control of a given DNS root zone is carried out by ICANN.
-
E.
DNSRegistryOperator
Indicates that an entity operates or manages a DNS registry service for domain names.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 28, 2026, 11:06 a.m.