Triple
T792245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monmouthshire County Council |
E16939
|
entity |
| Predicate | hasFinanceSource |
P9503
|
FINISHED |
| Object | council tax |
—
|
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: council tax | Statement: [Monmouthshire County Council, hasFinanceSource, council tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinanceSource Context triple: [Monmouthshire County Council, hasFinanceSource, council tax]
-
A.
hasWealthSource
chosen
Indicates that an entity derives its wealth or financial resources from a specified source.
-
B.
wealthSource
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
C.
hasFinancialInstitution
Indicates that one entity is associated with or linked to a financial institution, such as a bank or similar financial service provider.
-
D.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
-
E.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a798c7608190b9c79c52a1fe0859 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.