Triple
T16044171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eritrea–Ethiopia Claims Commission |
E389172
|
entity |
| Predicate | periodCoveredByClaims |
P3058
|
FINISHED |
| Object | 1998–2000 |
—
|
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: 1998–2000 | Statement: [Eritrea–Ethiopia Claims Commission, periodCoveredByClaims, 1998–2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodCoveredByClaims Context triple: [Eritrea–Ethiopia Claims Commission, periodCoveredByClaims, 1998–2000]
-
A.
timePeriodCoveredTo
chosen
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
previouslyCovered
Indicates that the subject has already been addressed, discussed, or dealt with at an earlier time or in a prior context.
-
C.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
D.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
E.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.