Triple
T26169789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zighoud Youcef |
E654367
|
entity |
| Predicate | namedForHistoricalEvent |
P92799
|
FINISHED |
| Object | Algerian War of Independence |
—
|
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: Algerian War of Independence | Statement: [Zighoud Youcef, namedForHistoricalEvent, Algerian War of Independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForHistoricalEvent Context triple: [Zighoud Youcef, namedForHistoricalEvent, Algerian War of Independence]
-
A.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
historicalEventsDescribed
Indicates that one entity (such as a document, text, or account) describes or recounts the historical events associated with another entity.
-
C.
historicEventAlsoKnownAs
Indicates that a historic event is referred to by an alternative name or alias.
-
D.
historicalEventDescribedAs
Indicates that a historical event is characterized or portrayed using a particular description, label, or narrative.
-
E.
hasHistoricSignificanceFor
chosen
Indicates that something holds notable historical importance or relevance for a particular entity or group.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 8:34 p.m.