Triple
T6030127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karlsruhe district administration |
E134279
|
entity |
| Predicate | hasBudgetFrom |
P27969
|
FINISHED |
| Object | district taxes and state allocations |
—
|
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: district taxes and state allocations | Statement: [Karlsruhe district administration, hasBudgetFrom, district taxes and state allocations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBudgetFrom Context triple: [Karlsruhe district administration, hasBudgetFrom, district taxes and state allocations]
-
A.
budgetFrom
chosen
Indicates that a budget or funding allocation originates from or is provided by a particular source.
-
B.
budgetPassedIs
Indicates that a proposed budget has been formally approved and passed.
-
C.
usesSalaryBudgets
Indicates that one entity allocates or manages financial resources for compensation based on predefined salary budgets associated with another entity.
-
D.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
E.
budgetLevel
Indicates the relative amount of financial resources allocated or available for something, typically categorized by level (e.g., low, medium, high).
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0561121708190a904e52aa3484988 |
completed | March 22, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.