Triple

T30845769
Position Surface form Disambiguated ID Type / Status
Subject Communes of Yvelines E785626 entity
Predicate hasLocalTaxationPower P79121 FINISHED
Object municipal 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: municipal taxes | Statement: [Communes of Yvelines, hasLocalTaxationPower, municipal taxes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalTaxationPower
Context triple: [Communes of Yvelines, hasLocalTaxationPower, municipal taxes]
  • A. hasLocalGovernmentJurisdictionOver
    Indicates that one governmental body possesses official authority to administer, regulate, and make binding decisions over a specific geographic area or population.
  • B. taxingJurisdiction chosen
    Indicates the authority or region that has the legal power to impose and collect taxes on a given entity or transaction.
  • C. hasMunicipalRightsInCountry
    Indicates that an entity possesses officially granted municipal rights or status within a specified country.
  • D. hasOwnTaxSystem
    Indicates that an entity maintains and administers its own distinct system of taxation, separate from other jurisdictions or authorities.
  • E. hasMunicipalTaxRate
    Indicates that a municipality imposes a specific tax rate within its jurisdiction.
  • 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_69f224b850848190a4af4ccf8ddadcdf completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fd4d1854988190be093b103a681798 completed May 8, 2026, 2:40 a.m.
PD Predicate disambiguation batch_69fd4c8d1a188190897c24527337814a completed May 8, 2026, 2:38 a.m.
Created at: April 29, 2026, 8:46 p.m.