Triple
T36214055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Uccialli |
E1047638
|
entity |
| Predicate | EthiopianRulerAtSigning |
P63848
|
FINISHED |
| Object | Menelik II |
—
|
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: Menelik II | Statement: [Treaty of Uccialli, EthiopianRulerAtSigning, Menelik II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EthiopianRulerAtSigning Context triple: [Treaty of Uccialli, EthiopianRulerAtSigning, Menelik II]
-
A.
reignAsNegusOfShewaStart
Indicates the time at which an individual begins their tenure ruling as Negus (king) of Shewa.
-
B.
signedByRuler
Indicates that an official document, decree, or agreement has been formally endorsed and authenticated through the signature of a ruling authority.
-
C.
peaceTreatyEgyptianLeader
Indicates that a peace treaty was established or signed involving an Egyptian leader as a principal party.
-
D.
treatySignedFor
Indicates that a formal treaty has been signed on behalf of, or in representation of, a particular entity, cause, or subject.
-
E.
wasSignatoryOf
chosen
Indicates that an entity formally signed or endorsed a specific document, agreement, or treaty as a participating party.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b57b8c5081909ba41145ba7753d1 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.