Triple
T12829478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heligoland–Zanzibar Treaty of 1890 |
E306745
|
entity |
| Predicate | effectOnZanzibar |
P58916
|
FINISHED |
| Object | confirmed British predominance over Zanzibar |
—
|
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: confirmed British predominance over Zanzibar | Statement: [Heligoland–Zanzibar Treaty of 1890, effectOnZanzibar, confirmed British predominance over Zanzibar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnZanzibar Context triple: [Heligoland–Zanzibar Treaty of 1890, effectOnZanzibar, confirmed British predominance over Zanzibar]
-
A.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
B.
effectOnOthers
chosen
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
C.
impactOnNizam
Indicates a relationship where one entity causes an effect, influence, or change on the Nizam (the governing authority or system).
-
D.
التأثير
Indicates a relationship where one entity produces a change or has an influence on another entity or its state.
-
E.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:34 p.m.