Triple
T10362142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catalan municipalities |
E244162
|
entity |
| Predicate | haveRevenueSource |
P13615
|
FINISHED |
| Object | local taxes |
—
|
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 taxes | Statement: [Catalan municipalities, haveRevenueSource, local taxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveRevenueSource Context triple: [Catalan municipalities, haveRevenueSource, local taxes]
-
A.
revenueSources
chosen
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
B.
hasWealthSource
Indicates that an entity derives its wealth or financial resources from a specified source.
-
C.
majorRevenueSource
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
-
D.
isCommissionSource
Indicates that one entity serves as the origin or basis from which another entity’s commission or referral fee is generated.
-
E.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e962f08c8190a7ac489dc524510d |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:59 a.m.