Triple
T33367686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ependes (FR) |
E854399
|
entity |
| Predicate | hasMunicipalityTypeCode |
P3943
|
FINISHED |
| Object | FR |
—
|
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: FR | Statement: [Ependes (FR), hasMunicipalityTypeCode, FR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalityTypeCode Context triple: [Ependes (FR), hasMunicipalityTypeCode, FR]
-
A.
hasMunicipalityType
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
B.
hasMunicipalityCode
chosen
Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
-
C.
hasMunicipalCodeJurisdiction
Indicates that an authority or entity holds official legal or regulatory power within a specific municipal code area or jurisdiction.
-
D.
hasMunicipalCodeAuthority
Indicates that an entity has the official power or jurisdiction to create, adopt, or enforce municipal codes, ordinances, or regulations.
-
E.
hasMunicipalAgencyType
Indicates that a municipal agency is classified as having a specific organizational or functional type.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 1:35 a.m.