Triple
T31429209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipal council of Malakoff |
E801746
|
entity |
| Predicate | budgetaryYearFollows |
P84343
|
FINISHED |
| Object | calendar year |
—
|
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: calendar year | Statement: [Municipal council of Malakoff, budgetaryYearFollows, calendar year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetaryYearFollows Context triple: [Municipal council of Malakoff, budgetaryYearFollows, calendar year]
-
A.
budgetFiscalYear
Indicates the fiscal year to which a particular budget or budgeting activity applies.
-
B.
budgetaryYearAlignment
chosen
Indicates that two or more entities have fiscal or budgetary years that coincide or are structured to match each other in timing and duration.
-
C.
fiscalYearHonored
Indicates that a particular fiscal year is formally recognized, celebrated, or given special acknowledgment in relation to an entity or event.
-
D.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
E.
lastSeparateBudgetYear
Indicates the most recent year in which the entities maintained or operated under separate budgets rather than a combined one.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:56 p.m.