Triple
T29361358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopia and Eritrea |
E744598
|
entity |
| Predicate | EthiopiaCurrency |
P2878
|
FINISHED |
| Object | Ethiopian birr |
—
|
NE NERFINISHED |
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: Ethiopian birr | Statement: [Ethiopia and Eritrea, EthiopiaCurrency, Ethiopian birr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EthiopiaCurrency Context triple: [Ethiopia and Eritrea, EthiopiaCurrency, Ethiopian birr]
-
A.
currencyNameInKinyarwanda
Indicates the name used for a given currency when expressed in the Kinyarwanda language.
-
B.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
C.
valueRelativeToAkçe
Indicates the value of something expressed in terms of, or relative to, the akçe monetary unit.
-
D.
currencyDepicted
Indicates that one entity visually represents or shows the image or symbol of a particular currency on it.
-
E.
isLegalTenderFor
chosen
Indicates that a particular currency or form of money is officially recognized by a governing authority as valid payment for debts and financial transactions within a specified jurisdiction.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6698892e88190b076bb0cdf159d8b |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 2:18 p.m.