Triple
T19716163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .at |
E473481
|
entity |
| Predicate | registry |
P86
|
FINISHED |
| Object |
nic.at GmbH
nic.at GmbH is the official organization responsible for managing and administering Austria’s .at country-code top-level domain.
|
E1391158
|
NE FINISHED |
How this triple was built (4 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: nic.at GmbH | Statement: [.at, registry, nic.at GmbH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: nic.at GmbH Context triple: [.at, registry, nic.at GmbH]
-
A.
NIC.TM
NIC.TM is the official domain registry responsible for managing and administering Turkmenistan’s country-code top-level domain, .tm.
-
B.
Slovak Telekom
Slovak Telekom is a major telecommunications provider in Slovakia offering mobile, fixed-line, and internet services.
-
C.
Swisscom
Swisscom is Switzerland’s leading telecommunications provider, offering mobile, fixed-line, internet, and digital TV services to consumers and businesses.
-
D.
Magyar Telekom
Magyar Telekom is Hungary’s leading telecommunications provider, offering mobile, fixed-line, and internet services as part of the Deutsche Telekom group.
-
E.
Telecom Italia
Telecom Italia is a major Italian telecommunications company that provides fixed-line, mobile, internet, and data services domestically and internationally.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: nic.at GmbH Triple: [.at, registry, nic.at GmbH]
Generated description
nic.at GmbH is the official organization responsible for managing and administering Austria’s .at country-code top-level domain.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: nic.at GmbH Target entity description: nic.at GmbH is the official organization responsible for managing and administering Austria’s .at country-code top-level domain.
-
A.
NIC.TM
NIC.TM is the official domain registry responsible for managing and administering Turkmenistan’s country-code top-level domain, .tm.
-
B.
Slovak Telekom
Slovak Telekom is a major telecommunications provider in Slovakia offering mobile, fixed-line, and internet services.
-
C.
Swisscom
Swisscom is Switzerland’s leading telecommunications provider, offering mobile, fixed-line, internet, and digital TV services to consumers and businesses.
-
D.
Magyar Telekom
Magyar Telekom is Hungary’s leading telecommunications provider, offering mobile, fixed-line, and internet services as part of the Deutsche Telekom group.
-
E.
Telecom Italia
Telecom Italia is a major Italian telecommunications company that provides fixed-line, mobile, internet, and data services domestically and internationally.
- F. None of above. chosen
Provenance (5 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440d96288190bfb732d2f8ceac79 |
completed | April 20, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07aba36954819085e53a67388086ab |
completed | May 15, 2026, 11:26 p.m. |
| NEDg | Description generation | batch_6a07ae091db48190a68d7744860bcb0e |
completed | May 15, 2026, 11:36 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a07aed8393481908f2bc48a3efc599a |
completed | May 15, 2026, 11:40 p.m. |
Created at: April 10, 2026, 1:46 p.m.