Triple
T4576546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .台湾 |
E123151
|
entity |
| Predicate | supportsSecondLevelDomains |
P42018
|
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: [.台湾, supportsSecondLevelDomains, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSecondLevelDomains Context triple: [.台湾, supportsSecondLevelDomains, yes]
-
A.
supportsSecondLevelRegistrations
chosen
Indicates that an entity allows or enables second-level domain registrations directly under it.
-
B.
secondLevelDomain
Indicates that one entity is the second-level domain associated with, or extracted from, another entity such as a full domain name or URL.
-
C.
exampleSecondLevelDomain
Indicates that one entity is an example of a second-level domain (the part of a domain name directly below a top-level domain) associated with another entity.
-
D.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
-
E.
supportsCustomDomain
Indicates that an entity provides the capability to use or configure a custom domain name instead of a default or system-assigned domain.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58dfe3508190b21836079e951a3c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.