Triple
T26287298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coutances arrondissement |
E661170
|
entity |
| Predicate | hasCoastalTowns |
P48746
|
FINISHED |
| Object | Granville |
—
|
NE NERFINISHED |
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: Granville | Statement: [Coutances arrondissement, hasCoastalTowns, Granville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalTowns Context triple: [Coutances arrondissement, hasCoastalTowns, Granville]
-
A.
hasCoastalMunicipalities
Indicates that a region or higher-level area includes one or more municipalities that are located along a sea or ocean coastline.
-
B.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
C.
includesCoastalTown
chosen
Indicates that a geographic area or region contains at least one town located on or directly adjacent to a coastline.
-
D.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
E.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 26, 2026, 10:05 p.m.