Triple
T36715522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algeria–European Union relations |
E906902
|
entity |
| Predicate | associationAgreementEnteredIntoForceYear |
P6161
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Algeria–European Union relations, associationAgreementEnteredIntoForceYear, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associationAgreementEnteredIntoForceYear Context triple: [Algeria–European Union relations, associationAgreementEnteredIntoForceYear, 2005]
-
A.
agreementYear
Indicates the calendar year in which an agreement between the related entities was made, signed, or came into effect.
-
B.
cameIntoForceInYear
chosen
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
-
C.
acquisitionAgreementYear
Indicates the calendar year in which an acquisition agreement between entities was made or came into effect.
-
D.
contractStartYear
Indicates the calendar year in which a contract between parties officially begins.
-
E.
treatySignedYear
Indicates the calendar year in which a specific treaty was formally signed.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.