Triple
T721789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunisian dinar |
E14631
|
entity |
| Predicate | exchangeControl |
P13312
|
FINISHED |
| Object | subject to Tunisian foreign exchange regulations |
—
|
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: subject to Tunisian foreign exchange regulations | Statement: [Tunisian dinar, exchangeControl, subject to Tunisian foreign exchange regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeControl Context triple: [Tunisian dinar, exchangeControl, subject to Tunisian foreign exchange regulations]
-
A.
exchangeControlRegime
chosen
Indicates a regulatory relationship where authority or control over something is transferred, shared, or swapped between parties under defined rules or regimes.
-
B.
exchangePolicy
Indicates the terms and conditions under which an item can be exchanged, including eligibility, time limits, and any applicable restrictions or requirements.
-
C.
exchange
Indicates a reciprocal transfer of something (such as goods, information, or services) between two or more entities.
-
D.
exchangeCode
Indicates a relationship where one entity trades or swaps a code with another entity, typically to obtain access, authorization, or some corresponding value in return.
-
E.
extensionMechanism
Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a591124c8190842e7ef18b064198 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.