Triple
T5219688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNMIK |
E117838
|
entity |
| Predicate | laterCurrencyFramework |
P8048
|
FINISHED |
| Object | euro in 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: euro in Kosovo | Statement: [UNMIK, laterCurrencyFramework, euro in Kosovo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCurrencyFramework Context triple: [UNMIK, laterCurrencyFramework, euro in Kosovo]
-
A.
successorMonetarySystem
chosen
Indicates that one monetary system directly follows and replaces another in time or function.
-
B.
currencyInitiative
Indicates an initiative, program, or action specifically related to the development, regulation, promotion, or reform of a currency or monetary system.
-
C.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
D.
reintroducedCurrencyOf
Indicates that a currency has been brought back into use as legal tender in a particular country or region after having been previously replaced, discontinued, or suspended.
-
E.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ab6e63c8190964b2b65a0206134 |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.