Triple

T9291228
Position Surface form Disambiguated ID Type / Status
Subject Aisne E223521 entity
Predicate subprefecture P9697 FINISHED
Object Vervins E507470 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: Vervins | Statement: [Aisne, subprefecture, Vervins]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vervins
Context triple: [Aisne, subprefecture, Vervins]
  • A. Vervins chosen
    Vervins is a commune in the Aisne department of northern France, known historically for the 1598 Treaty of Vervins between France and Spain.
  • B. Clamecy
    Clamecy is a historic commune in central France known for its medieval architecture and former timber-floating industry along the Yonne River.
  • C. Badonviller
    Badonviller is a small commune in northeastern France, known as the birthplace of the astronomer Charles Messier.
  • D. Cambrésis
    Cambrésis is a historic region in northern France centered around the city of Cambrai, known for its medieval bishopric and strategic importance in European conflicts.
  • E. Huningue
    Huningue is a small French commune in the Alsace region near the borders with Germany and Switzerland, historically notable as a fortified border town.
  • 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_69ca8422ddf881908a3f8f876c9f53aa completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd0865a7108190b807afd259980db2 completed April 1, 2026, 11:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0b2381e2c8190acbecf97dea1200c completed April 4, 2026, 6:39 a.m.
Created at: March 30, 2026, 7:35 p.m.