Triple

T35257837
Position Surface form Disambiguated ID Type / Status
Subject Merbes-le-Château E1018281 entity
Predicate hasHistoricVillageSetting P59339 FINISHED
Object true 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: true | Statement: [Merbes-le-Château, hasHistoricVillageSetting, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricVillageSetting
Context triple: [Merbes-le-Château, hasHistoricVillageSetting, true]
  • A. hasHistoricVillageArea chosen
    Indicates that an entity includes or is associated with an area recognized as a historic village or traditional settlement zone.
  • B. hasHistoricVillagesAlong
    Indicates that a route, path, or geographic feature has historic villages located along its course or in close proximity to it.
  • C. hasHistoricTownRights
    Indicates that an entity possesses officially granted historic town rights, typically conferring a traditional legal or municipal status as a town.
  • D. hasHistoricSetting
    Indicates that something is set in, or takes place within, a historically significant time period or location.
  • E. hasMedievalVillageCenter
    Indicates that an entity includes or is associated with a central area characteristic of a medieval village, such as its main hub of settlement or activity.
  • 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_69f76de407d081909dfc3c419817ae93 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff3e1762d8819089a60e402e682817 completed May 9, 2026, 2 p.m.
PD Predicate disambiguation batch_69ff3d8c6f308190a0646b1432752eb8 completed May 9, 2026, 1:58 p.m.
Created at: May 3, 2026, 4:02 p.m.