Triple
T142475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pound sterling |
E2882
|
entity |
| Predicate | rankByReserveHoldings |
P6797
|
FINISHED |
| Object | one of top global reserve currencies |
—
|
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: one of top global reserve currencies | Statement: [Pound sterling, rankByReserveHoldings, one of top global reserve currencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankByReserveHoldings Context triple: [Pound sterling, rankByReserveHoldings, one of top global reserve currencies]
-
A.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
B.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
C.
rankBySize
Indicates that entities are ordered or compared based on their size.
-
D.
selectionRankingEndPoint
Indicates the position or boundary in an ordered list at which a selection or ranking process concludes.
-
E.
selectionRankingFrequency
Indicates how often an entity is chosen or ranked in a particular position within a selection or ordering process.
- F. None of above. chosen
Provenance (4 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.