Triple
T33126360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transitional Government of Ethiopia |
E847733
|
entity |
| Predicate | adoptedCharter |
P13720
|
FINISHED |
| Object | Transitional Period Charter of Ethiopia |
—
|
NE NERFINISHED |
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: Transitional Period Charter of Ethiopia | Statement: [Transitional Government of Ethiopia, adoptedCharter, Transitional Period Charter of Ethiopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedCharter Context triple: [Transitional Government of Ethiopia, adoptedCharter, Transitional Period Charter of Ethiopia]
-
A.
charterAdoptedIn
Indicates that a charter was formally adopted or enacted at a specific time or in a specific place.
-
B.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
C.
charterRevised
Indicates that an existing charter has been modified or updated from its previous version.
-
D.
adoptedDocument
chosen
Indicates that an authoritative body has formally approved and accepted a specific document as official or binding.
-
E.
hasCharter
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:27 a.m.