Triple
T1406051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constantine |
E31693
|
entity |
| Predicate | historicEventRole |
P17461
|
FINISHED |
| Object | center of resistance during French conquest of Algeria |
—
|
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: center of resistance during French conquest of Algeria | Statement: [Constantine, historicEventRole, center of resistance during French conquest of Algeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicEventRole Context triple: [Constantine, historicEventRole, center of resistance during French conquest of Algeria]
-
A.
significantEventRole
chosen
Indicates that an entity plays an important or defining role in a particular significant event.
-
B.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
ceremonialRoleInPeriod
Indicates that an entity holds or fulfills a specific ceremonial role during a defined time period.
-
D.
historicEventAlsoKnownAs
Indicates that a historic event is referred to by an alternative name or alias.
-
E.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bc55a08190a4dfe13a5378aff3 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.