Triple
T25715249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bléré |
E644844
|
entity |
| Predicate | municipalStatusStart |
P23872
|
FINISHED |
| Object | French Revolution era |
—
|
NE NERFINISHED |
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: French Revolution era | Statement: [Bléré, municipalStatusStart, French Revolution era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalStatusStart Context triple: [Bléré, municipalStatusStart, French Revolution era]
-
A.
isMunicipalStatus
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
B.
previousMunicipalityStatus
Indicates that one municipality previously held a particular municipal status or classification before a change occurred.
-
C.
hasMunicipalStatusUntil
Indicates that an entity possessed municipal status up to, but not beyond, a specified point in time.
-
D.
hasMunicipalStatusChange
Indicates that an entity undergoes a change in its official municipal status (e.g., creation, upgrade, downgrade, merger, or dissolution as a municipality).
-
E.
municipalityEstablished
chosen
Indicates that a municipality was officially created or founded at a specific point in time.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 9:40 p.m.