Triple
T4700385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croatian kuna |
E104254
|
entity |
| Predicate | ISO4217Code |
P189
|
FINISHED |
| Object | HRK |
E104254
|
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: HRK | Statement: [Croatian kuna, ISO4217Code, HRK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HRK Context triple: [Croatian kuna, ISO4217Code, HRK]
-
A.
HRK
HRK is the German Rectors' Conference, a voluntary association representing the interests of universities and other higher education institutions in Germany.
-
B.
Croatian kuna
chosen
The Croatian kuna was the national currency of Croatia from 1994 until its replacement by the euro in 2023.
-
C.
IN-HR
IN-HR is the ISO 3166-2 code representing the Indian state of Haryana.
-
D.
Croatian dinar
The Croatian dinar was the transitional currency of Croatia used in the early 1990s after independence, before being replaced by the Croatian kuna.
-
E.
HRP
HRP is a high-level long-distance hiking route that traverses the Pyrenees along or near the French–Spanish border from the Atlantic Ocean to the Mediterranean Sea.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd63cbc5d881908d1d40c60929b253 |
completed | March 20, 2026, 3:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be03ca24848190aa7df32472647cae |
completed | March 21, 2026, 2:34 a.m. |
Created at: March 20, 2026, 1:17 p.m.