Triple
T24892745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flers-lez-Lille |
E623047
|
entity |
| Predicate | timeOfMunicipalReorganization |
P14846
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Flers-lez-Lille, timeOfMunicipalReorganization, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMunicipalReorganization Context triple: [Flers-lez-Lille, timeOfMunicipalReorganization, 20th century]
-
A.
municipalityReform
Indicates a formal reorganization or restructuring of a municipality’s administrative boundaries, governance, or status.
-
B.
partOfAdministrativeDivisionReform
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
C.
reorganizationYear
Indicates the year in which an entity underwent a structural or organizational reorganization.
-
D.
hasTerritoryReorganizedInto
Indicates that an entity’s territorial boundaries or administrative divisions have been restructured to form another specified territory.
-
E.
reorganizationPeriod
chosen
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
- 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:26 a.m.