Triple

T20210056
Position Surface form Disambiguated ID Type / Status
Subject Gladrags Wizardwear E493465 entity
Predicate hasBranchIn P49773 FINISHED
Object Paris NE NERFINISHED

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: [Gladrags Wizardwear, hasBranchIn, Paris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paris
Context triple: [Gladrags Wizardwear, hasBranchIn, Paris]
  • A. Paris
    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 chosen
    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 an American hip hop artist and producer known for his politically charged, socially conscious lyrics and militant themes.
  • E. Paris
    Paris is a budget-oriented AMD Sempron processor core designed for entry-level desktop computing.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da6269614c8190bb40475d9d477358 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66ed4706c81908a5e4a3023a9c22f completed April 20, 2026, 6:22 p.m.
Created at: April 11, 2026, 11:38 p.m.