Triple
T14052138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shilling–pound system |
E338117
|
entity |
| Predicate | subdivisionOfShilling |
P39839
|
FINISHED |
| Object | penny |
—
|
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: penny | Statement: [shilling–pound system, subdivisionOfShilling, penny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionOfShilling Context triple: [shilling–pound system, subdivisionOfShilling, penny]
-
A.
officialCurrencySubunitOf
Indicates that one unit represents the official fractional subunit (e.g., cents to a dollar) of a specified currency.
-
B.
currencySubunitOf
chosen
Indicates that a monetary subunit (such as cents) is a fractional unit belonging to and defined in terms of a larger base currency.
-
C.
minorDenomination
Indicates that one entity is a smaller or subordinate unit of currency or value in relation to another entity.
-
D.
minorUnitSubdivisions
Indicates that one administrative or organizational unit is subdivided into smaller, subordinate units.
-
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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8bc54c8190a12f0fc056568538 |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.