Triple

T11978429
Position Surface form Disambiguated ID Type / Status
Subject Western Anatolia E285093 entity
Predicate containsHistoricalSite P1098 FINISHED
Object Hierapolis E128079 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: Hierapolis | Statement: [Western Anatolia, containsHistoricalSite, Hierapolis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hierapolis
Context triple: [Western Anatolia, containsHistoricalSite, Hierapolis]
  • A. Hierapolis chosen
    Hierapolis was an ancient Greco-Roman city in Phrygia (modern-day Turkey), known for its hot springs and as an early center of Christianity.
  • B. Hierapolis Bambyce
    Hierapolis Bambyce was an important ancient Syrian city, famed as a major religious center dedicated to the goddess Atargatis and known in later times as Manbij.
  • C. Aspendos
    Aspendos is an ancient Greco-Roman city in southern Turkey renowned for its remarkably well-preserved Roman theater.
  • 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_69d6ab2eaeb881909f7914758f859413 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90393cfb08190b5b45d3e5e32fad3 completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60a5b024c81909e4ccfd7dec7edb3 completed May 2, 2026, 2:29 p.m.
Created at: April 8, 2026, 9:46 p.m.