Triple
T30644470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milan Township Fiscal Officer |
E780081
|
entity |
| Predicate | dataManaged |
P38791
|
FINISHED |
| Object | township budgets |
—
|
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: township budgets | Statement: [Milan Township Fiscal Officer, dataManaged, township budgets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataManaged Context triple: [Milan Township Fiscal Officer, dataManaged, township budgets]
-
A.
dataManagement
chosen
Indicates the relationship in which an entity organizes, stores, maintains, and governs data throughout its lifecycle.
-
B.
dataMaintained
Indicates that one entity is responsible for preserving, storing, or keeping another entity’s data up to date and accessible over time.
-
C.
data
Indicates that one entity serves as informational content, measurements, or recorded values associated with another entity.
-
D.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
E.
dataControl
Indicates that one entity has the authority or capability to determine how another entity’s data is collected, used, shared, or managed.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a58cd808190bc1cdaa106291084 |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:29 p.m.