Triple
T5206506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipality of Cusco |
E117522
|
entity |
| Predicate | hasBudgetSource |
P4841
|
FINISHED |
| Object | local taxes |
—
|
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: local taxes | Statement: [Municipality of Cusco, hasBudgetSource, local taxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBudgetSource Context triple: [Municipality of Cusco, hasBudgetSource, local taxes]
-
A.
budgetSource
chosen
Indicates the origin or provider of the funds used to finance a particular activity, project, or expenditure.
-
B.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
C.
usesSalaryBudgets
Indicates that one entity allocates or manages financial resources for compensation based on predefined salary budgets associated with another entity.
-
D.
hasMonetaryGrant
Indicates that an entity provides or receives a monetary grant from another entity.
-
E.
budgetaryAuthorityWith
Indicates that one entity has formal control or decision-making power over the allocation and use of another entity’s financial resources.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a4a7b7c8190af5a7149f8fe4f87 |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.