Triple

T8551474
Position Surface form Disambiguated ID Type / Status
Subject Rubenid dynasty E202453 entity
Predicate capital P234 FINISHED
Object Tarsus E47685 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: Tarsus | Statement: [Rubenid dynasty, capital, Tarsus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tarsus
Context triple: [Rubenid dynasty, capital, Tarsus]
  • A. Tarsus chosen
    Tarsus is an ancient city in Cilicia (in modern-day Turkey) known as a major cultural and commercial center of the Roman Empire and as the birthplace of the Apostle Paul.
  • B. Smyrna
    Smyrna was a major Aegean port city (modern-day İzmir in Turkey) that served as a key commercial and cultural hub in the Ottoman Empire.
  • C. Smyrna
    Smyrna is a suburban city in the Atlanta metropolitan area known for its residential communities, parks, and proximity to major Atlanta attractions.
  • D. Edessa
    Edessa is a historic city in northern Greece renowned for its picturesque waterfalls and ancient heritage.
  • E. Edessa
    Edessa was an ancient city in Upper Mesopotamia, renowned as a major early center of Syriac Christianity and culture.
  • 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_69ca832610e08190b3b6c6cd2c250255 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe886fb788190a73e7c76c4f86409 completed March 31, 2026, 3:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce6dc7f6fc8190addd5d2bbe1f4408 completed April 2, 2026, 1:23 p.m.
Created at: March 30, 2026, 6:19 p.m.