Triple
T11411168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouest |
E270373
|
entity |
| Predicate | servedCity |
P3936
|
FINISHED |
| Object | Granville |
E170610
|
NE 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: Granville | Statement: [Ouest, servedCity, Granville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Granville Context triple: [Ouest, servedCity, Granville]
-
A.
Granville
chosen
Granville is a coastal town in Normandy, France, known for its historic port, seaside resorts, and views toward the Chausey Islands.
-
B.
Granville
Granville is a locality and suburb within Queensland’s Fraser Coast Region in Australia.
-
C.
Granville
Granville is a masculine given name of English origin that has been borne by various notable individuals, including artists, politicians, and scholars.
-
D.
Ouistreham
Ouistreham is a coastal town in Normandy, France, known for its ferry port and its location at the eastern end of the D-Day landing area of Sword Beach.
-
E.
Wereham
Wereham is a small rural village in Norfolk, England, known for its historic church and traditional village green.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8015017d08190b4020c76545556d6 |
completed | April 9, 2026, 7:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b855f0508190a2e57ef9407ddb1a |
completed | April 20, 2026, 5:23 a.m. |
Created at: April 8, 2026, 9:34 p.m.