Triple

T23303092
Position Surface form Disambiguated ID Type / Status
Subject King Ravine E590357 entity
Predicate hasTrail P3625 FINISHED
Object Chemin des Dames 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: Chemin des Dames | Statement: [King Ravine, hasTrail, Chemin des Dames]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chemin des Dames
Context triple: [King Ravine, hasTrail, Chemin des Dames]
  • A. Chemin des Dames ridge chosen
    The Chemin des Dames ridge is a strategically important high ground in northern France that was the scene of intense and costly fighting during World War I.
  • B. Verdun
    Verdun is a tram stop on the Tramway de Tours network in the city of Tours, France.
  • C. Verdun
    Verdun is a borough of Montreal, Quebec, known for its historic waterfront along the St. Lawrence River and its mix of residential neighborhoods and urban amenities.
  • D. Pozières
    Pozières is a small village in northern France best known as the site of intense fighting during the Battle of the Somme in World War I.
  • E. Battle of Verdun
    The Battle of Verdun was one of the longest and bloodiest engagements of World War I, symbolizing the brutal attrition warfare on the Western Front between France and Germany in 1916.
  • 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_69e25d1c0ecc8190a355aa229f06d0e0 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1972406a08190bbf355cc7a9f8432 completed April 29, 2026, 5:29 a.m.
Created at: April 17, 2026, 5:04 p.m.