Triple
T25734380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulon |
E645333
|
entity |
| Predicate | isPartOfRegionType |
P174654
|
FINISHED |
| Object | rural 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: rural commune | Statement: [Boulon, isPartOfRegionType, rural commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfRegionType Context triple: [Boulon, isPartOfRegionType, rural commune]
-
A.
isTypeOfRegion
Indicates that one entity is classified as a specific type or category of region in relation to another entity.
-
B.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
C.
containsRegionType
Indicates that one region includes or encompasses another region of a specified type within its spatial or logical boundaries.
-
D.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
E.
regionalType
Indicates the classification of a region according to its designated type or category within a broader geographic or administrative system.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6c5b7e46081909975b05f7298cc0e |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c49069e48190a3486b6254a6645b |
completed | May 3, 2026, 3:44 a.m. |
Created at: April 21, 2026, 11:21 p.m.