Triple

T4850711
Position Surface form Disambiguated ID Type / Status
Subject Roman province of Asia E108406 entity
Predicate majorCity P316 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: [Roman province of Asia, majorCity, Hierapolis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hierapolis
Context triple: [Roman province of Asia, majorCity, 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. Aspendos
    Aspendos is an ancient Greco-Roman city in southern Turkey renowned for its remarkably well-preserved Roman theater.
  • C. Edessa
    Edessa is a historic city in northern Greece renowned for its picturesque waterfalls and ancient heritage.
  • D. Edessa
    Edessa was an ancient city in Upper Mesopotamia, renowned as a major early center of Syriac Christianity and culture.
  • E. Perge
    Perge is an ancient Greco-Roman city in southern Turkey renowned for its well-preserved ruins, including a stadium, theater, and colonnaded streets.
  • 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_69bd440a89548190a5f14ba6da6b97dc completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6d1ffad48190bec7be4a3b5ebb9c completed March 20, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69be5cdefda8819095fbc04446bf32f5 completed March 21, 2026, 8:54 a.m.
Created at: March 20, 2026, 1:25 p.m.