Triple

T13655097
Position Surface form Disambiguated ID Type / Status
Subject canton of Vauréal E326839 entity
Predicate containsAdministrativeTerritorialEntity P747 FINISHED
Object Ennery E738425 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: Ennery | Statement: [canton of Vauréal, containsAdministrativeTerritorialEntity, Ennery]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ennery
Context triple: [canton of Vauréal, containsAdministrativeTerritorialEntity, Ennery]
  • A. Ennery chosen
    Ennery is a commune in the Val-d'Oise department in northern France, situated near Pontoise in the Île-de-France region.
  • B. Ennesi
    Ennesi are the inhabitants or natives of the city of Enna in central Sicily, Italy.
  • C. Enerhen
    Enerhen is a town in Delta State, Nigeria, situated within the Udu area of the Warri metropolitan region and known for its role in the local oil and gas economy.
  • D. Eshnunna
    Eshnunna was an important ancient Mesopotamian city-state in the Diyala River region, known for its early legal code and strategic role in Old Babylonian politics and trade.
  • E. Enniger
    Enniger is a village and district within the town of Ennigerloh in North Rhine-Westphalia, Germany.
  • 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_69d8076d8270819092afc2f0e9c359a8 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc60ace048190a4b92310ba272bd1 completed April 12, 2026, 4:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69f78b03083c8190855a2a4ee44e4098 completed May 3, 2026, 5:50 p.m.
Created at: April 9, 2026, 9:52 p.m.