Triple
T1048596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TW |
E22640
|
entity |
| Predicate | hasRelatedCcTLD |
P13209
|
FINISHED |
| Object | .tw |
—
|
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: .tw | Statement: [TW, hasRelatedCcTLD, .tw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedCcTLD Context triple: [TW, hasRelatedCcTLD, .tw]
-
A.
relatedTLD
chosen
Indicates that one top-level domain (TLD) has an association or connection with another TLD, such as similarity, shared purpose, or contextual relevance.
-
B.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
C.
hasCcf
Indicates that one entity possesses, is associated with, or is characterized by a specific CCF (the exact nature of which is defined elsewhere in the model or ontology).
-
D.
hasRelatedCategory
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
-
E.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.