Triple

T10185362
Position Surface form Disambiguated ID Type / Status
Subject Mor Afrem E236894 entity
Predicate associatedWith P37 FINISHED
Object Nisibis E236895 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: Nisibis | Statement: [Mor Afrem, associatedWith, Nisibis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nisibis
Context triple: [Mor Afrem, associatedWith, Nisibis]
  • A. Nisibis chosen
    Nisibis was an important ancient city in Mesopotamia, strategically located on key trade routes and known as a center of early Syriac Christianity and learning.
  • B. Edessa
    Edessa is a historic city in northern Greece renowned for its picturesque waterfalls and ancient heritage.
  • C. Edessa
    Edessa was an ancient city in Upper Mesopotamia, renowned as a major early center of Syriac Christianity and culture.
  • D. Ctesiphon
    Ctesiphon was an ancient metropolis on the Tigris River that served for centuries as the principal capital of the Parthian and later Sasanian Persian empires.
  • E. Ṭarābulus
    Ṭarābulus is the Arabic name for Tripoli, a major historic port city and the capital of Libya on the Mediterranean coast.
  • 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_69ca84d7260c8190bfbec36762943f37 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cded36e9808190b385c5aec4889e00 completed April 2, 2026, 4:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69d317a4d99c8190941322d3de2998f5 completed April 6, 2026, 2:17 a.m.
Created at: March 30, 2026, 9:12 p.m.