Triple
T12198720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiltshire Council |
E290655
|
entity |
| Predicate | isFundingSource |
P43183
|
FINISHED |
| Object | local services in Wiltshire |
—
|
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 services in Wiltshire | Statement: [Wiltshire Council, isFundingSource, local services in Wiltshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFundingSource Context triple: [Wiltshire Council, isFundingSource, local services in Wiltshire]
-
A.
fundingInstrument
chosen
Indicates that one entity serves as the financial source, mechanism, or tool used to provide funding for another entity or activity.
-
B.
authorizesFundingFor
Indicates that one entity grants official approval or permission for financial resources to be provided to another entity or purpose.
-
C.
secondaryFundingSource
Indicates that an entity has an additional, non-primary source of financial support or funding.
-
D.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
E.
funderType
Indicates the category or kind of organization or individual that provides funding in the relationship.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.