Triple
T12530230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clichy-sous-Bois |
E299542
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Gagny |
E28558
|
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: Gagny | Statement: [Clichy-sous-Bois, locatedNear, Gagny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gagny Context triple: [Clichy-sous-Bois, locatedNear, Gagny]
-
A.
Gagny
chosen
Gagny is a suburban commune in the eastern outskirts of Paris, France, known primarily as a residential town within the Seine-Saint-Denis department.
-
B.
Givry
Givry is a Burgundy wine appellation in eastern France, noted for its predominantly Pinot Noir red wines with a reputation for good value and quality.
-
C.
Cugny
Cugny is a locality within the municipality of Bernex in the canton of Geneva, Switzerland.
-
D.
Santenay
Santenay is a wine-producing village in Burgundy, France, known for its predominantly red wines made from Pinot Noir and its location at the southern end of the Côte de Beaune.
-
E.
Potigny
Potigny is a commune in the Calvados department of the Normandy region in northwestern France.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95469d100819087c83bc55e3ec9ce |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5e7daa08190917f446c06adece3 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 8, 2026, 9:57 p.m.