Triple
T22482062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Callinicum |
E555790
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Callinicum |
—
|
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: Callinicum | Statement: [Battle of Callinicum, location, Callinicum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Callinicum Context triple: [Battle of Callinicum, location, Callinicum]
-
A.
Edessa
Edessa is a historic city in northern Greece renowned for its picturesque waterfalls and ancient heritage.
-
B.
Edessa
chosen
Edessa was an ancient city in Upper Mesopotamia, renowned as a major early center of Syriac Christianity and culture.
-
C.
Diocaesarea
Diocaesarea is the Roman-era name for the ancient Galilean city of Sepphoris, a major administrative and cultural center near Nazareth.
-
D.
Anazarbus
Anazarbus was an important ancient city in the region of Cilicia, in what is now southern Turkey, known for its strategic location and impressive fortifications.
-
E.
Hadrianopolis
Hadrianopolis was an important ancient Roman and Byzantine city in Thrace, later known as Edirne in modern-day Turkey.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3a3b688190b41599979d038d85 |
completed | April 29, 2026, 1:17 a.m. |
Created at: April 16, 2026, 8:49 p.m.