Triple
T1858131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EEC |
E41751
|
entity |
| Predicate | createdCustomsUnion |
P11448
|
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: [EEC, createdCustomsUnion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdCustomsUnion Context triple: [EEC, createdCustomsUnion, true]
-
A.
establishedCustomsUnion
chosen
Indicates that one entity has created or formally instituted a customs union agreement with another entity, eliminating internal tariffs and adopting common external trade policies.
-
B.
hasCustomsUnion
Indicates that two or more entities participate in a customs union, sharing a common external tariff and removing customs duties between them.
-
C.
hasCurrencyUnion
Indicates that two or more entities share a common official currency through a formal monetary or currency union.
-
D.
allianceCreated
Indicates that a formal cooperative relationship or partnership has been established between two or more parties.
-
E.
createdImmigrationBarrier
Indicates that one entity established or imposed a restriction, policy, or obstacle that makes it more difficult for another entity to immigrate or cross a border.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.