Triple
T29361333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopia and Eritrea |
E744598
|
entity |
| Predicate | normalizationEffort |
P166790
|
FINISHED |
| Object | 2018 peace declaration |
—
|
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: 2018 peace declaration | Statement: [Ethiopia and Eritrea, normalizationEffort, 2018 peace declaration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normalizationEffort Context triple: [Ethiopia and Eritrea, normalizationEffort, 2018 peace declaration]
-
A.
normalizationAttempt
Indicates an effort to convert something into a standard or consistent form according to defined rules or criteria.
-
B.
normalizationInvolves
Indicates that a normalization process includes or makes use of a particular component, step, or element as part of its execution.
-
C.
normalizationType
Indicates the specific method or scheme used to normalize or standardize data, values, or representations within a given context.
-
D.
normalizationAgreement
chosen
Indicates a formal agreement or process through which previously conflicting or non-standard relations, conditions, or practices are brought into a mutually accepted, standardized, or regularized state.
-
E.
refinesNormalization
Indicates that one normalization process or scheme improves, clarifies, or makes more precise another existing normalization.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:18 p.m.