Triple
T19294252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arrondissement of Largentière |
E482519
|
entity |
| Predicate | hasINSEECodeType |
P27964
|
FINISHED |
| Object | arrondissement code |
—
|
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: arrondissement code | Statement: [arrondissement of Largentière, hasINSEECodeType, arrondissement code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasINSEECodeType Context triple: [arrondissement of Largentière, hasINSEECodeType, arrondissement code]
-
A.
inseeCode
chosen
Indicates the official INSEE (French national statistics institute) code assigned to an entity, typically identifying a specific geographic or administrative unit.
-
B.
formerINSEECode
Indicates that an entity was previously identified by a different INSEE code before being assigned its current one.
-
C.
hasCadastralCode
Indicates that an entity is associated with a specific cadastral (land registry) identification code.
-
D.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
E.
hasFrenchSector
Indicates that an entity includes, controls, or is associated with a sector or area designated as French.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc84500c81908ac53711335ad2d9 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.