Triple

T17702209
Position Surface form Disambiguated ID Type / Status
Subject Battle of Royan E441334 entity
Predicate location P40 FINISHED
Object Royan 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: Royan | Statement: [Battle of Royan, location, Royan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Royan
Context triple: [Battle of Royan, location, 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. Shahrud
    Shahrud is a major city in northeastern Iran known as an important regional hub for transportation, agriculture, and access to nearby natural attractions such as the Alborz Mountains and desert landscapes.
  • C. Neyshabur
    Neyshabur is a historic city in northeastern Iran renowned for its cultural heritage, turquoise mines, and as the resting place of poet and polymath Omar Khayyam.
  • D. Nurabad
    Nurabad is a city in western Iran that serves as a local urban center within Lorestan Province.
  • E. Rudbar
    Rudbar is a city in northern Iran known for its olive production and location within the mountainous Gilan Province.
  • 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4715c3980819094b080a871df1100 completed April 19, 2026, 6:08 a.m.
Created at: April 10, 2026, 10:05 a.m.