Triple
T2219894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cypriot pound |
E48115
|
entity |
| Predicate | preDecimalSubunit |
P32237
|
FINISHED |
| Object | 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: shilling | Statement: [Cypriot pound, preDecimalSubunit, shilling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preDecimalSubunit Context triple: [Cypriot pound, preDecimalSubunit, shilling]
-
A.
officialCurrencySubunitOf
Indicates that one unit represents the official fractional subunit (e.g., cents to a dollar) of a specified currency.
-
B.
decimalized
Indicates that something has been converted into or expressed in decimal form, typically changing from another numeral or measurement system to a base-10 representation.
-
C.
minorUnitSubdivisions
Indicates that one administrative or organizational unit is subdivided into smaller, subordinate units.
-
D.
fractionalUnitSymbol
Indicates the symbolic notation used to represent the fractional unit associated with a given quantity or measurement.
-
E.
minorUnitsPerUnit
chosen
Indicates the number of smaller sub-units that collectively make up one whole unit in a given measurement or currency system.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc01386588190a9507f2969a201ca |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.