Triple

T14091600
Position Surface form Disambiguated ID Type / Status
Subject Picpus Fathers E339144 entity
Predicate foundedInCity P263 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: [Picpus Fathers, foundedInCity, Paris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paris
Context triple: [Picpus Fathers, foundedInCity, 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_69d81c687b0c819087fd9ed4198403f8 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5ee3213c8190af2853a2a5b302a2 completed April 14, 2026, 3:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd090350881909dd6ff12ec7e61dd completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:21 p.m.