Triple
T19716195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .at |
E473481
|
entity |
| Predicate | supportsNameserversAbroad |
P137051
|
FINISHED |
| Object | yes |
—
|
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 | Statement: [.at, supportsNameserversAbroad, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNameserversAbroad Context triple: [.at, supportsNameserversAbroad, yes]
-
A.
supportsInternationalRegistrars
Indicates that an entity is compatible with and provides services for registrars operating in multiple countries or international markets.
-
B.
supportsWHOIS
Indicates that one entity provides or is compatible with WHOIS lookup functionality for another entity.
-
C.
supportsRDAP
Indicates that one entity provides or is compatible with RDAP (Registration Data Access Protocol) functionality for another entity.
-
D.
IDNSupport
Indicates that an entity provides or enables support for Internationalized Domain Names (IDNs), such as registering, resolving, or handling domain names with non-ASCII characters.
-
E.
supportsCountry
Indicates that one entity provides assistance, endorsement, or backing to a specific country.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440d96288190bfb732d2f8ceac79 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.