Triple

T22978256
Position Surface form Disambiguated ID Type / Status
Subject Cortaillod E571385 entity
Predicate hasNeighbor P5707 FINISHED
Object Rochefort 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: Rochefort | Statement: [Cortaillod, hasNeighbor, Rochefort]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rochefort
Context triple: [Cortaillod, hasNeighbor, Rochefort]
  • A. Rochefort
    Rochefort is a historic French port town on the Atlantic coast known for its naval heritage and maritime museum sites.
  • B. Rochefort
    Rochefort is a town in the Walloon region of Belgium, known for its historic abbey and Trappist beer.
  • C. Rochefort chosen
    Rochefort is a municipality in the canton of Neuchâtel in western Switzerland.
  • D. Rochefort-sur-Loire
    Rochefort-sur-Loire is a commune in western France’s Loire Valley, known for its vineyards and production of sweet white wines within the Coteaux du Layon appellation.
  • E. Rochefort-en-Terre
    Rochefort-en-Terre is a picturesque medieval village in Brittany, France, renowned for its well-preserved stone architecture and status as one of the country’s most beautiful villages.
  • 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_69e245b3c50481908bb3741ec9f40862 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18293f830819095cca91af7abd742 completed April 29, 2026, 4:01 a.m.
Created at: April 17, 2026, 3:49 p.m.