Triple
T31562972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavray-sur-Sienne |
E805319
|
entity |
| Predicate | hasFormerCommune |
P5557
|
FINISHED |
| Object | Gavray |
—
|
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: Gavray | Statement: [Gavray-sur-Sienne, hasFormerCommune, Gavray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerCommune Context triple: [Gavray-sur-Sienne, hasFormerCommune, Gavray]
-
A.
formerMunicipalityOf
chosen
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
B.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
C.
isCommune
Indicates that an entity functions as or has the status of a commune, typically a local administrative or municipal unit.
-
D.
hasFormerCounty
Indicates that an entity was previously part of, or administered by, a particular county in the past but no longer is.
-
E.
hasFormerSettlement
Indicates that a location previously contained a settlement that no longer exists or is no longer inhabited.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 30, 2026, 10:16 p.m.