Triple

T14278242
Position Surface form Disambiguated ID Type / Status
Subject Trajanopolis E353971 entity
Predicate hasHistoricalName P2834 FINISHED
Object Traianopolis E198007 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: Traianopolis | Statement: [Trajanopolis, hasHistoricalName, Traianopolis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Traianopolis
Context triple: [Trajanopolis, hasHistoricalName, Traianopolis]
  • A. Traianopolis chosen
    Traianopolis was an ancient Roman city in Thrace, founded by Emperor Trajan and situated along the important Via Egnatia trade and military route.
  • B. Târgoviște
    Târgoviște is a historic city in southern Romania, known as a former Wallachian capital and the site where Nicolae Ceaușescu was executed in 1989.
  • C. Reghin
    Reghin is a town in central Romania known for its traditional violin-making industry and location in Mureș County, Transylvania.
  • D. Sinaia
    Sinaia is a Romanian mountain resort town in the Carpathians, famed for Peleș Castle and its historic role as a royal summer residence.
  • E. Silistra
    Silistra is a historic city in northeastern Bulgaria on the Danube River, known as an important cultural and economic center of the Dobruja region.
  • 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_69d8278d25148190abf1a8c8f5f533ad completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de6585270c8190a717127b2f5dab3b completed April 14, 2026, 4:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd326f62b4819084b1e984678991ae completed May 8, 2026, 12:46 a.m.
Created at: April 10, 2026, 1:10 a.m.