Triple
T12612542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colossae |
E301162
|
entity |
| Predicate | supersededBy |
P101
|
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: [Colossae, supersededBy, Hierapolis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hierapolis Context triple: [Colossae, supersededBy, 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954eaf8d08190a06abb6918253acd |
completed | April 10, 2026, 7:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b86935c8190835f6a407be52ae3 |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:12 p.m.