Triple

T6957031
Position Surface form Disambiguated ID Type / Status
Subject Patouès E161269 entity
Predicate relatedTo P37 FINISHED
Object Arpitan E52559 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: Arpitan | Statement: [Patouès, relatedTo, Arpitan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arpitan
Context triple: [Patouès, relatedTo, Arpitan]
  • A. Arpitan chosen
    Arpitan is a Romance language traditionally spoken in parts of France, Switzerland, and Italy, particularly in the Alpine region.
  • B. Arpitanie
    Arpitanie is a cultural and linguistic region in parts of France, Switzerland, and Italy where the Arpitan (Franco-Provençal) language and related traditions are historically rooted.
  • C. La Salle
    La Salle was the former name of the French industrial town now known as Decazeville, historically associated with coal mining in the Aveyron department.
  • D. La Salle
    La Salle is a small alpine municipality in Italy’s Aosta Valley, known for its scenic mountain landscapes and proximity to Mont Blanc.
  • E. Arpitans
    Arpitans are a Romance-speaking ethnolinguistic group native to the Alpine regions of France, Switzerland, and Italy, traditionally associated with the Arpitan (Franco-Provençal) language and culture.
  • 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_69c68852a9a0819097797e31d492e273 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dad0e52081908b524dc6a66bab01 completed March 27, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7588e2c5c8190a66a0205f3c2bf99 completed March 28, 2026, 4:26 a.m.
Created at: March 27, 2026, 2:29 p.m.