Triple
T12333704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .ai |
E294025
|
entity |
| Predicate | supportsRDAP |
P104551
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [.ai, supportsRDAP, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRDAP Context triple: [.ai, supportsRDAP, true]
-
A.
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.
-
B.
DNSSECSupported
Indicates that a domain or DNS service supports and correctly implements DNSSEC security extensions for authenticating DNS data.
-
C.
regulatoryDomainSupported
Indicates that an entity is compatible with, and can operate under, a specified regulatory domain or jurisdiction.
-
D.
supportsRelayAgents
Indicates that one entity is capable of working with or providing functionality for relay agents that forward or mediate communications between other entities.
-
E.
supportsRDS
Indicates that one entity provides compatibility, resources, or functionality necessary for the operation or use of an RDS (Relational Database Service) instance.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f64ad20819080d99e57833b4b51 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.