Triple

T13930014
Position Surface form Disambiguated ID Type / Status
Subject 16e législature de la Ve République E334964 entity
Predicate ville P76028 FINISHED
Object Paris E568 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: Paris | Statement: [16e législature de la Ve République, ville, Paris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paris
Context triple: [16e législature de la Ve République, ville, Paris]
  • A. Paris chosen
    Paris is the capital and largest city of France, renowned for its historic architecture, art, fashion, and cultural influence worldwide.
  • B. Paris
    Paris is a prince of Troy in Greek mythology, best known for judging the beauty contest of the goddesses and for abducting Helen, which sparked the Trojan War.
  • C. Paris
    Paris is a major Chilean department store and retail chain offering a wide range of apparel, home goods, and consumer products.
  • D. Paris
    Paris is a budget-oriented AMD Sempron processor core designed for entry-level desktop computing.
  • E. Paris
    Paris was an enslaved man held in bondage by George Washington at the President's House in Philadelphia during his presidency.
  • 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_69d81c5f739081908bc05b2461f54828 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2aa900a0819095eeb1bc46b0336e completed April 14, 2026, 11:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69fbac802b7081909b36eebe85374594 completed May 6, 2026, 9:02 p.m.
Created at: April 9, 2026, 10:16 p.m.