Triple
T7188451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abraham Accords |
E167627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | normalization agreement |
C20931
|
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: normalization agreement Context triple: [Abraham Accords, instanceOf, normalization agreement]
-
A.
naming agreement
A naming agreement is a legal contract in which one party grants another the right to use a specific name (such as a personal, brand, or facility name) under defined terms and conditions.
-
B.
conciliation rules
Conciliation rules are structured guidelines or procedures designed to facilitate the amicable resolution of disputes between parties through negotiation and compromise, often with the assistance of a neutral third party.
-
C.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
-
D.
annex to international agreement
An annex to an international agreement is a supplementary document formally attached to the main treaty that provides detailed provisions, technical specifications, or additional obligations that are integral to and legally binding under the agreement.
-
E.
normative guideline
A normative guideline is a prescriptive rule or principle that defines how things ought to be done or how people ought to behave within a particular context or system.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:50 p.m.