Triple

T2899957
Position Surface form Disambiguated ID Type / Status
Subject People’s Municipal Assembly of Algiers E62630 entity
Predicate usesBudgetType P2120 FINISHED
Object municipal budget 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: municipal budget | Statement: [People’s Municipal Assembly of Algiers, usesBudgetType, municipal budget]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesBudgetType
Context triple: [People’s Municipal Assembly of Algiers, usesBudgetType, municipal budget]
  • A. budgetType chosen
    Indicates the classification or category of a budget associated with an entity or financial activity.
  • B. usesSalaryBudgets
    Indicates that one entity allocates or manages financial resources for compensation based on predefined salary budgets associated with another entity.
  • C. budgetFrom
    Indicates that a budget or funding allocation originates from or is provided by a particular source.
  • D. budgetRight
    Indicates that an entity has the authority, responsibility, or entitlement to allocate, manage, or decide on the use of a specified budget or financial resources.
  • E. supportsSpendingCategory
    Indicates that one entity allows, enables, or is compatible with making expenditures in a specified spending category.
  • 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_69ab4c3e070c8190b78d3d2c005876dd completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abe0b081308190af8875151fb11c4e completed March 7, 2026, 8:24 a.m.
PD Predicate disambiguation batch_69abdd19bac881908f047d616aca8438 completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 10:10 p.m.