Triple

T19909418
Position Surface form Disambiguated ID Type / Status
Subject Fragments of Papias E478505 entity
Predicate placeOfOrigin P3743 FINISHED
Object Hierapolis 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: Hierapolis | Statement: [Fragments of Papias, placeOfOrigin, Hierapolis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hierapolis
Context triple: [Fragments of Papias, placeOfOrigin, 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. Doliche
    Doliche was an ancient city of Perrhaebia in northern Thessaly, Greece, known from classical historical and geographical sources.
  • D. Aspendos
    Aspendos is an ancient Greco-Roman city in southern Turkey renowned for its remarkably well-preserved Roman theater.
  • E. Edessa
    Edessa is a historic city in northern Greece renowned for its picturesque waterfalls and ancient heritage.
  • 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_69d8e520682081909892916424699bd5 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6598e7d988190b8759100a147f2c1 completed April 20, 2026, 4:51 p.m.
Created at: April 10, 2026, 1:53 p.m.