Triple

T5021820
Position Surface form Disambiguated ID Type / Status
Subject Bourg-la-Reine E112868 entity
Predicate locatedSouthOf P9676 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: [Bourg-la-Reine, locatedSouthOf, Paris]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paris
Context triple: [Bourg-la-Reine, locatedSouthOf, 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. Parigi
    Parigi is a coastal town that serves as the administrative center of Parigi Moutong Regency in Central Sulawesi, Indonesia.
  • D. Lyon
    Lyon is a major city in east-central France known for its historical and architectural landmarks, gastronomy, and role as a key economic and cultural center.
  • E. Paris Bar
    The Paris Bar is the professional association and regulatory body for lawyers practicing in Paris, France.
  • 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_69bd4435c2f48190be593158cbfcf8a3 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73656edc8190b802ad38d9552b58 completed March 20, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69be92557c508190a8c27b974906999f completed March 21, 2026, 12:43 p.m.
Created at: March 20, 2026, 1:36 p.m.