Triple
T14512857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCC member states |
E340440
|
entity |
| Predicate | shareCurrencyPlan |
P66084
|
FINISHED |
| Object | proposed GCC common currency |
—
|
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: proposed GCC common currency | Statement: [GCC member states, shareCurrencyPlan, proposed GCC common currency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareCurrencyPlan Context triple: [GCC member states, shareCurrencyPlan, proposed GCC common currency]
-
A.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
-
B.
allianceCurrencySharing
chosen
Indicates that members of an alliance share or coordinate the use, management, or benefits of a common currency or monetary system.
-
C.
shareEUFunds
Indicates that one entity allocates or distributes European Union funds to another entity.
-
D.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
E.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6c6054819086b4c0ce1d83fdc5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.