Triple
T525367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Mesnil-Amelot |
E10904
|
entity |
| Predicate | municipalStatus |
P852
|
FINISHED |
| Object | commune |
—
|
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: commune | Statement: [Le Mesnil-Amelot, municipalStatus, commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalStatus Context triple: [Le Mesnil-Amelot, municipalStatus, commune]
-
A.
hasMunicipalStatusChange
Indicates that an entity undergoes a change in its official municipal status (e.g., creation, upgrade, downgrade, merger, or dissolution as a municipality).
-
B.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
C.
municipality
chosen
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
D.
hasMunicipalService
Indicates that a municipality provides or is responsible for a specific public service to a given area, facility, or population.
-
E.
presentDayMunicipality
Indicates that one entity is the current-day municipality encompassing or corresponding to the area or jurisdiction of another (typically historical) entity.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b7f448819087e5e7f3b37d7142 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.