Triple
T30731195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Association Agreement with the European Union (Jordan–EU) |
E782427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | association agreement |
C57699
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: association agreement Context triple: [Association Agreement with the European Union (Jordan–EU), instanceOf, association agreement]
-
A.
association agreement component
An association agreement component is a modular element within a broader agreement that defines specific terms, conditions, or relationships between associated parties or entities.
-
B.
public association
A public association is a voluntary, non-profit organization formed by individuals or entities to pursue shared interests or goals that serve or involve the broader community.
-
C.
partnership agreement
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
-
D.
federal association
A federal association is an organization formed by multiple member entities (such as states, regions, or groups) that collaborate under a shared federal structure while retaining a degree of autonomy.
-
E.
free association agreement
A free association agreement is a voluntary, non-binding arrangement between parties to collaborate or exchange ideas without creating formal legal obligations or restrictive commitments.
- F. None of above. chosen
Provenance (1 batch)
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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:37 p.m.