Triple

T14089788
Position Surface form Disambiguated ID Type / Status
Subject Avenue Foch E339096 entity
Predicate terminusNear P1866 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: [Avenue Foch, terminusNear, Porte Dauphine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Porte Dauphine
Context triple: [Avenue Foch, terminusNear, 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_69d81c687b0c819087fd9ed4198403f8 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5ee3213c8190af2853a2a5b302a2 completed April 14, 2026, 3:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd0a7aab88190949cf1fd8e11b050 completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:21 p.m.