Triple
T33542014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sèvremoine |
E859094
|
entity |
| Predicate | hasFormerCommuneStatus |
P5557
|
FINISHED |
| Object | Le Longeron |
—
|
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: Le Longeron | Statement: [Sèvremoine, hasFormerCommuneStatus, Le Longeron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerCommuneStatus Context triple: [Sèvremoine, hasFormerCommuneStatus, Le Longeron]
-
A.
containsFormerMunicipality
Indicates that an administrative unit includes within its boundaries an area that was previously an independent municipality.
-
B.
formerMunicipalityOf
chosen
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
C.
hasVoivodeshipStatusInPast
Indicates that an entity previously held the status of a voivodeship (administrative region) but no longer does so.
-
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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 1, 2026, 1:39 a.m.