Triple
T18919037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrondissement of Avranches |
E462796
|
entity |
| Predicate | contains |
P35
|
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: [Arrondissement of Avranches, contains, Granville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Granville Context triple: [Arrondissement of Avranches, contains, 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.
Granville
Granville is a town in Washington County, New York, known for its slate quarrying history and location near the Vermont border.
-
E.
Schupferville
Schupferville is the former name of the small town now known as Juliaetta in Latah County, Idaho.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c629527481909dad169f07df0da4 |
completed | April 20, 2026, 6:22 a.m. |
Created at: April 10, 2026, 11:59 a.m.