Triple

T8788438
Position Surface form Disambiguated ID Type / Status
Subject TER Nouvelle-Aquitaine E209099 entity
Predicate servesCity P82 FINISHED
Object Royan E255664 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: Royan | Statement: [TER Nouvelle-Aquitaine, servesCity, Royan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Royan
Context triple: [TER Nouvelle-Aquitaine, servesCity, Royan]
  • A. Royan chosen
    Royan is a seaside resort town on France’s Atlantic coast, known for its beaches and post-war modernist architecture.
  • B. Iranshahr
    Iranshahr is a city in southeastern Iran known as an administrative and cultural center within the Sistan and Baluchestan region.
  • C. Andimeshk
    Andimeshk is a city in southwestern Iran known as a regional transportation hub and gateway to the Zagros Mountains.
  • D. Sadras
    Sadras is a historic coastal town in Tamil Nadu, India, known for its Dutch-era fort and role as a former trading port on the Coromandel Coast.
  • E. Margilan
    Margilan is a historic city in eastern Uzbekistan renowned as a traditional center of silk production and trade along the Silk Road.
  • 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_69ca836168108190bb43d3dc235c1f55 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5f89a84c819085d4cfe4e6dfbda8 completed March 31, 2026, 11:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf5210454c8190aa83d941893a4bc5 completed April 3, 2026, 5:37 a.m.
Created at: March 30, 2026, 6:43 p.m.