Triple

T14676739
Position Surface form Disambiguated ID Type / Status
Subject Arve E344664 entity
Predicate locatedIn P40 FINISHED
Object Romandy E2947 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: Romandy | Statement: [Arve, locatedIn, Romandy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Romandy
Context triple: [Arve, locatedIn, Romandy]
  • A. Romandy chosen
    Romandy is the French-speaking western region of Switzerland, encompassing cantons such as Geneva, Vaud, Neuchâtel, and Jura.
  • B. Neuchâtelois
    Neuchâtelois refers to the inhabitants or natives of the Canton of Neuchâtel in western Switzerland, known for their French-speaking culture and heritage.
  • C. Valentinois
    Valentinois are the inhabitants or natives of Valence, a city in the Drôme department of southeastern France.
  • D. Swiss French
    Swiss French is the variety of the French language spoken in the French‑speaking regions of Switzerland, characterized by distinctive vocabulary, pronunciation, and some regional usages.
  • E. Lia Rumantscha
    Lia Rumantscha is the main organization dedicated to promoting, standardizing, and preserving the Romansh language in Switzerland.
  • 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_69d822e34b348190ada4d1cdb6c7c226 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb567c2b88190a9639e61b6fba7df completed April 14, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fde17e5a1c8190b1bf5565eab9d519 completed May 8, 2026, 1:13 p.m.
Created at: April 10, 2026, 1:27 a.m.