Triple
T17034043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val-de-Reuil |
E413273
|
entity |
| Predicate | communeStatus |
P45139
|
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: [Val-de-Reuil, communeStatus, commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communeStatus Context triple: [Val-de-Reuil, communeStatus, commune]
-
A.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
B.
singleCommuneProvince
Indicates that a province contains exactly one commune within its administrative boundaries.
-
C.
isRuralCommune
Indicates that the subject entity is classified as a rural commune, i.e., an administrative unit characterized by predominantly non-urban, countryside or village-based settlement.
-
D.
capitalOfCommune
Indicates that one place serves as the administrative capital or chief town of a given commune.
-
E.
humanSettlementStatus
chosen
Indicates the classification of a place in terms of its status as a human settlement (e.g., whether and how it is recognized or designated as a populated place).
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8eea4448190bd2eed88de2b4e73 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.