Triple
T3113548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ugandan shilling |
E65004
|
entity |
| Predicate | denominationExampleCoin |
P2872
|
FINISHED |
| Object | 50 Ugandan shillings |
—
|
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: 50 Ugandan shillings | Statement: [Ugandan shilling, denominationExampleCoin, 50 Ugandan shillings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationExampleCoin Context triple: [Ugandan shilling, denominationExampleCoin, 50 Ugandan shillings]
-
A.
coinDenomination
chosen
Indicates the specific monetary value assigned to a coin within a currency system.
-
B.
denominationType
Indicates the specific category or kind of denomination associated with an entity, such as its type within a broader classification of denominations.
-
C.
denominationDepicted
Indicates that an item visually represents or shows the monetary denomination (value) of a currency.
-
D.
denominationName
Indicates the specific religious or organizational denomination to which an entity belongs or is associated.
-
E.
denomination
Indicates the specific religious or organizational branch, sect, or subgroup with which an entity is affiliated.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada43c79448190aa72f707319e8c5e |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.