Triple

T14223551
Position Surface form Disambiguated ID Type / Status
Subject Parc Floral de Paris E352558 entity
Predicate operator P179 FINISHED
Object City of 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: City of Paris | Statement: [Parc Floral de Paris, operator, City of Paris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Paris
Context triple: [Parc Floral de Paris, operator, City of Paris]
  • A. Parigi
    Parigi is a coastal town that serves as the administrative center of Parigi Moutong Regency in Central Sulawesi, Indonesia.
  • B. Paris chosen
    Paris is the capital and largest city of France, renowned for its historic architecture, art, fashion, and cultural influence worldwide.
  • 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 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.
  • 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_69d8278a06e481908b5d6af0a8afe737 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6227c288819081473ce44f9f0934 completed April 14, 2026, 3:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd4c29b4e08190896ddde5096628d3 completed May 8, 2026, 2:36 a.m.
Created at: April 10, 2026, 1:06 a.m.