Triple
T31136136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Normandy |
E793645
|
entity |
| Predicate | formerINSEERegionCode |
P199106
|
FINISHED |
| Object | 23 |
—
|
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: 23 | Statement: [Upper Normandy, formerINSEERegionCode, 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerINSEERegionCode Context triple: [Upper Normandy, formerINSEERegionCode, 23]
-
A.
formerNameOfRegion
Indicates that one name was previously used for a region that is now known by a different name.
-
B.
formerRegionBefore2016
Indicates that an entity was recognized as a region prior to the year 2016 but no longer holds that regional status after 2016.
-
C.
formerNUTSCode
Indicates that an entity was previously identified by a specific NUTS (Nomenclature of Territorial Units for Statistics) regional code that is no longer current.
-
D.
formerAutonomousRegion
Indicates that an entity was previously an autonomous region but no longer holds that status.
-
E.
formerAdministrativeTerritory
Indicates that one entity was previously an official administrative territory of another entity but no longer holds that status.
- F. None of above. chosen
Provenance (4 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
| PDg | Predicate description generation | batch_69ff1f3ee3588190a857d1504c93be8b |
completed | May 9, 2026, 11:49 a.m. |
Created at: April 29, 2026, 9:05 p.m.