Triple
T13812255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ligne 2 |
E331921
|
entity |
| Predicate | hasStation |
P35
|
FINISHED |
| Object | Porte Dauphine |
E68454
|
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: Porte Dauphine | Statement: [Ligne 2, hasStation, Porte Dauphine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Porte Dauphine Context triple: [Ligne 2, hasStation, Porte Dauphine]
-
A.
Porte Dauphine
chosen
Porte Dauphine is a Paris Métro station on Line 2, located near the Bois de Boulogne in the 16th arrondissement of Paris.
-
B.
Porte Soubeyran
Porte Soubeyran is a historic medieval city gate in Manosque, France, notable as one of the remaining vestiges of the town’s ancient fortifications.
-
C.
Porte Saint-Jacques
Porte Saint-Jacques is a historic medieval city gate in Parthenay, France, notable for its well-preserved fortifications and role in the town’s ancient defensive walls.
-
D.
Porte du Soubeyran
Porte du Soubeyran is a historic medieval city gate and landmark in the town of Marvejols in southern France.
-
E.
Porte de la Gardette
Porte de la Gardette is a historic city gate in the medieval fortified town of Aigues-Mortes in southern 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de027198f8819095da3e714ac241f5 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c70454a8819097b5e5091f84be33 |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:12 p.m.