Triple
T36492600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann Arbor Police Department |
E899089
|
entity |
| Predicate | budgetCovers |
P102389
|
FINISHED |
| Object | personnel costs |
—
|
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: personnel costs | Statement: [Ann Arbor Police Department, budgetCovers, personnel costs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetCovers Context triple: [Ann Arbor Police Department, budgetCovers, personnel costs]
-
A.
coversCosts
Indicates that one party assumes responsibility for paying or reimbursing the expenses incurred by another party.
-
B.
hasBudgetFor
chosen
Indicates that an entity possesses sufficient allocated financial resources to support, fund, or carry out another specified entity, activity, or purpose.
-
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.
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.
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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.