Triple

T31319514
Position Surface form Disambiguated ID Type / Status
Subject Capussa E798689 entity
Predicate historicTerritoryLocation P199418 FINISHED
Object modern 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: modern Algeria | Statement: [Capussa, historicTerritoryLocation, modern Algeria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicTerritoryLocation
Context triple: [Capussa, historicTerritoryLocation, modern Algeria]
  • A. historicalRegion
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • B. historicalGeographyOf
    Indicates the relationship in which one entity concerns, analyzes, or describes the historical geography (past spatial patterns, landscapes, and territorial changes) of another entity.
  • C. historicalTerritoryType
    Indicates that a territory is classified according to a specific type or category it held during a historical period.
  • D. historicallyImportantRegion
    Indicates that a region holds significant importance due to its impact on historical events, developments, or cultural heritage.
  • E. historicLocationType
    Indicates the specific kind or category of a place based on its historical significance or role.
  • 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_69f224e1932c81908fef14f7b03a10b7 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69ff38b960808190a8263348f1e5c0e4 completed May 9, 2026, 1:38 p.m.
PD Predicate disambiguation batch_69ff37d97d9c8190849b2bac14f9af1d completed May 9, 2026, 1:34 p.m.
PDg Predicate description generation batch_69ff38b8843c819097359a4d77e9d442 completed May 9, 2026, 1:38 p.m.
Created at: April 29, 2026, 9:15 p.m.