Triple
T25312314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .pl country-code top-level domain |
E634638
|
entity |
| Predicate | IDNSupported |
P42016
|
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: [.pl country-code top-level domain, IDNSupported, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IDNSupported Context triple: [.pl country-code top-level domain, IDNSupported, true]
-
A.
IDNSupport
chosen
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.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
C.
isSupportedFor
Indicates that one entity provides compatibility, assistance, or backing necessary for another entity’s proper use or operation.
-
D.
regulatoryDomainSupported
Indicates that an entity is compatible with, and can operate under, a specified regulatory domain or jurisdiction.
-
E.
supportsRDAP
Indicates that one entity provides or is compatible with RDAP (Registration Data Access Protocol) functionality for 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939f4e58819095eba5792f55f07c |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:27 p.m.