Triple
T20204575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayor of Tianeti |
E493314
|
entity |
| Predicate | budgetTypeManaged |
P139184
|
FINISHED |
| Object | municipal budget of Tianeti |
—
|
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 of Tianeti | Statement: [Mayor of Tianeti, budgetTypeManaged, municipal budget of Tianeti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetTypeManaged Context triple: [Mayor of Tianeti, budgetTypeManaged, municipal budget of Tianeti]
-
A.
budgetType
Indicates the classification or category of a budget associated with an entity or financial activity.
-
B.
budgetingSystem
Indicates a system or process used to plan, allocate, track, and control financial resources or budgets.
-
C.
budgetFrom
Indicates that a budget or funding allocation originates from or is provided by a particular source.
-
D.
budgetAccount
Indicates a relationship where an entity is associated with, charged to, or managed under a specific budget account for financial tracking or allocation.
-
E.
budgetItemOf
Indicates that one entity is a specific budget line or allocation that belongs to, or is part of, another entity’s overall budget.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66d8f90108190b72e37c0056de0f8 |
completed | April 20, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:38 p.m.