Triple
T34619842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigerian pound |
E888970
|
entity |
| Predicate | subunitToShilling |
P8012
|
FINISHED |
| Object | 12 pence = 1 shilling |
—
|
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: 12 pence = 1 shilling | Statement: [Nigerian pound, subunitToShilling, 12 pence = 1 shilling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subunitToShilling Context triple: [Nigerian pound, subunitToShilling, 12 pence = 1 shilling]
-
A.
valueInShillings
Indicates the monetary amount of something expressed specifically in shillings.
-
B.
currencySubunitOf
Indicates that a monetary subunit (such as cents) is a fractional unit belonging to and defined in terms of a larger base currency.
-
C.
historicalSubunitToUnit
chosen
Indicates that one entity was historically a subunit, subdivision, or component of another larger entity.
-
D.
officialCurrencySubunitOf
Indicates that one unit represents the official fractional subunit (e.g., cents to a dollar) of a specified currency.
-
E.
historicalSubunit
Indicates that one entity functioned as a subordinate or component part of another entity during a specific historical period, but is no longer in that role in the present.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.