Triple
T5451380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterling area |
E122377
|
entity |
| Predicate | usedExchangeControls |
P35645
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sterling area, usedExchangeControls, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedExchangeControls Context triple: [Sterling area, usedExchangeControls, true]
-
A.
exchangeControlRegime
Indicates a regulatory relationship where authority or control over something is transferred, shared, or swapped between parties under defined rules or regimes.
-
B.
exchangeControlLink
Indicates a relationship where control or authority over something is transferred or swapped between entities through a defined linkage or mechanism.
-
C.
exchangeControlManagedBy
Indicates that the management or oversight of an exchange’s operations or controls is carried out by a specified managing entity.
-
D.
exchangedFor
Indicates that one entity has been traded or substituted in return for another entity.
-
E.
exchangeRegime
chosen
Indicates the type of currency exchange system or policy framework governing how a country’s currency is valued and traded relative to other currencies.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.