Triple
T24470364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Algiers (1815) |
E617080
|
entity |
| Predicate | barbaryStateInvolved |
P156226
|
FINISHED |
| Object | 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: Algiers | Statement: [Treaty of Algiers (1815), barbaryStateInvolved, Algiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barbaryStateInvolved Context triple: [Treaty of Algiers (1815), barbaryStateInvolved, Algiers]
-
A.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
-
B.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
C.
colonialConflictWith
Indicates a relationship in which two entities are engaged in a conflict arising from or occurring within a colonial context, typically involving control, resistance, or domination.
-
D.
battlesWith
Indicates that two entities are engaged in active conflict, combat, or struggle against each other.
-
E.
endedBilateralWarBetween
Indicates that an action or event brought a bilateral war between two parties to a conclusion or cessation.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.