Triple

T21541106
Position Surface form Disambiguated ID Type / Status
Subject Treaty of 562 E531489 entity
Predicate placeSigned P441 FINISHED
Object Constantinople 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: Constantinople | Statement: [Treaty of 562, placeSigned, Constantinople]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Constantinople
Context triple: [Treaty of 562, placeSigned, Constantinople]
  • A. Constantinople (probable) chosen
    Constantinople (probable) refers to the historic capital of the Byzantine Empire, a major political, cultural, and economic center that is now modern-day Istanbul in Turkey.
  • B. Byzas
    Byzas is the legendary Greek founder of the ancient city of Byzantium, later known as Constantinople and Istanbul.
  • C. İznik
    İznik is a historic town in northwestern Turkey, renowned as the site of the First Council of Nicaea and for its rich Byzantine and Ottoman heritage.
  • D. Trebizond mint
    The Trebizond mint was a provincial Ottoman coin-producing facility located in the historic Black Sea port city of Trebizond (modern Trabzon).
  • E. Istanbul
    Istanbul is a major Ethereum network upgrade that introduced performance improvements, reduced gas costs for certain operations, and enhanced the platform’s overall scalability and security.
  • 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_69e0c45f17148190949c330ab9c27706 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee9d12b264819096f844b5833198aa completed April 26, 2026, 11:17 p.m.
Created at: April 16, 2026, 6:28 p.m.