Triple
T23819415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Tampon |
E589188
|
entity |
| Predicate | hasMunicipalStatusInFrance |
P37705
|
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: [Le Tampon, hasMunicipalStatusInFrance, commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalStatusInFrance Context triple: [Le Tampon, hasMunicipalStatusInFrance, commune]
-
A.
isMunicipalStatus
chosen
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
B.
isMunicipalFormationOf
Indicates that one administrative unit is formally established and recognized as the municipal formation corresponding to another territorial or administrative entity.
-
C.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
D.
hasMunicipalFlag
Indicates that a municipality possesses an officially recognized flag associated with it.
-
E.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7ad0ec88190bace5c3f00908b30 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:59 p.m.