Triple
T13958479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bordeaux Métropole |
E335728
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Saint-Jean-d’Illac |
E874611
|
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: Saint-Jean-d’Illac | Statement: [Bordeaux Métropole, contains, Saint-Jean-d’Illac]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saint-Jean-d’Illac Context triple: [Bordeaux Métropole, contains, Saint-Jean-d’Illac]
-
A.
Saint-Jean-d’Illac
chosen
Saint-Jean-d’Illac is a commune in southwestern France’s Gironde department, situated near Bordeaux and known for its forested surroundings and residential character.
-
B.
Juillac
Juillac is a rural commune in central France’s Corrèze department, known for its traditional Limousin countryside and agricultural character.
-
C.
Saint-Jean-d'Heurs
Saint-Jean-d'Heurs is a small commune in the Puy-de-Dôme department in central France.
-
D.
Saint-Jean-de-Losne
Saint-Jean-de-Losne is a historic river port town in eastern France, known as an important inland waterways hub on the Saône River.
-
E.
Rillieux-la-Pape
Rillieux-la-Pape is a suburban commune in eastern France, located near Lyon in the Rhône department.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7a34f08190aa0d88b66154f268 |
completed | April 14, 2026, 12:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1d490048190b28cb44dd4ec46c4 |
completed | May 6, 2026, 8:17 p.m. |
Created at: April 9, 2026, 10:17 p.m.