Triple
T9281995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .xk |
E223090
|
entity |
| Predicate | usedPending |
P87375
|
FINISHED |
| Object | assignment of an official ISO-based TLD for Kosovo |
—
|
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: assignment of an official ISO-based TLD for Kosovo | Statement: [.xk, usedPending, assignment of an official ISO-based TLD for Kosovo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPending Context triple: [.xk, usedPending, assignment of an official ISO-based TLD for Kosovo]
-
A.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
B.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
C.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
D.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
E.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081c2b048190aa6930de3bf2f87f |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:34 p.m.