Triple
T784427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Albania |
E16569
|
entity |
| Predicate | currency |
P245
|
FINISHED |
| Object | Albanian lek |
E75649
|
NE 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: Albanian lek | Statement: [Kingdom of Albania, currency, Albanian lek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Albanian lek Context triple: [Kingdom of Albania, currency, Albanian lek]
-
A.
Albanian lek
chosen
The Albanian lek is the official monetary unit of Albania, used for everyday transactions and financial operations throughout the country.
-
B.
Macedonian denar
The Macedonian denar is the official fiat currency used in North Macedonia for everyday transactions and monetary policy.
-
C.
Yugoslav dinar
The Yugoslav dinar was the former national currency of socialist and later federal Yugoslavia, known for multiple revaluations amid periods of high inflation before the country's breakup.
-
D.
Serbian dinar
The Serbian dinar is the official national currency of Serbia, used for everyday transactions and monetary policy.
-
E.
Bulgarian lev
The Bulgarian lev is the official national currency of Bulgaria, subdivided into 100 stotinki and pegged to the euro through a currency board arrangement.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a769dc6481908f12e872f997acf3 |
completed | March 1, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a6733c2e608190962440d6ef637784 |
completed | March 3, 2026, 5:35 a.m. |
Created at: March 1, 2026, 7:37 p.m.