Triple

T9169308
Position Surface form Disambiguated ID Type / Status
Subject Paris Convention of 1919 E220042 entity
Predicate placeSigned P441 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: [Paris Convention of 1919, placeSigned, Paris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paris
Context triple: [Paris Convention of 1919, placeSigned, 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. Parigi
    Parigi is a coastal town that serves as the administrative center of Parigi Moutong Regency in Central Sulawesi, Indonesia.
  • 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_69ca83e467108190abcae6a33b3d4dad completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccaae0f3148190b111b22902cdb86c completed April 1, 2026, 5:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d05be87434819090caedc38bf55123 completed April 4, 2026, 12:31 a.m.
Created at: March 30, 2026, 7:22 p.m.