Triple
T36715519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algeria–European Union relations |
E906902
|
entity |
| Predicate | associationAgreementSignedWith |
P205015
|
FINISHED |
| Object | European Union |
E4332
|
NE 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: European Union | Statement: [Algeria–European Union relations, associationAgreementSignedWith, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associationAgreementSignedWith Context triple: [Algeria–European Union relations, associationAgreementSignedWith, European Union]
-
A.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
B.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
C.
agencySignedWith
Indicates that a formal agreement or contract has been established between an agency and another party.
-
D.
lastAgreementSignedWith
Indicates that one entity is the most recent party with whom another entity has signed an agreement.
-
E.
rightsAgreementSignedWith
Indicates that a formal rights agreement has been executed and signed between two parties.
- F. None of above. chosen
Provenance (5 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dde4fb6008190910eddfe98ca9d5c |
completed | June 26, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.