Triple
T15978367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addis Ababa Agreement |
E387507
|
entity |
| Predicate | effectivelyAbrogatedIn |
P46419
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Addis Ababa Agreement, effectivelyAbrogatedIn, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectivelyAbrogatedIn Context triple: [Addis Ababa Agreement, effectivelyAbrogatedIn, 1983]
-
A.
abolishedInEffectBy
Indicates that the legal force or practical operation of something is nullified or terminated as a result of another specified action or measure.
-
B.
usedToAbrogate
Indicates that something served as the means or instrument by which a rule, law, agreement, or obligation was annulled, repealed, or rendered no longer valid.
-
C.
abrogatedAlongWith
Indicates that one thing was abolished, repealed, or annulled at the same time as another, as part of a linked or joint termination.
-
D.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
E.
abolishedInPractice
chosen
Indicates that, although not formally revoked, the action or institution is no longer carried out or enforced in actual practice.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.