Triple
T24470369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Algiers (1815) |
E617080
|
entity |
| Predicate | signedByRulerOfAlgiers |
P81589
|
FINISHED |
| Object | Dey of Algiers |
—
|
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: Dey of Algiers | Statement: [Treaty of Algiers (1815), signedByRulerOfAlgiers, Dey of Algiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedByRulerOfAlgiers Context triple: [Treaty of Algiers (1815), signedByRulerOfAlgiers, Dey of Algiers]
-
A.
signedByRuler
chosen
Indicates that an official document, decree, or agreement has been formally endorsed and authenticated through the signature of a ruling authority.
-
B.
signedTreatyAt
Indicates that an entity formally entered into and endorsed a treaty at a specific location.
-
C.
signedUnderMonarch
Indicates that a document or agreement was formally signed during the reign or authority of a specific monarch.
-
D.
wasSignatoryOf
Indicates that an entity formally signed or endorsed a specific document, agreement, or treaty as a participating party.
-
E.
MoroccanConcession
Indicates a diplomatic or commercial concession granted in the context of Moroccan affairs or territory.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299432b2881909502f9cbc7e4dbb0 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.