Triple
T11191580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | river Siris |
E264814
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Heraclea |
E227683
|
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: Heraclea | Statement: [river Siris, near, Heraclea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heraclea Context triple: [river Siris, near, Heraclea]
-
A.
Heraclea
chosen
Heraclea was an important ancient Greek city in southern Italy’s Lucania region, known for its strategic location and role in Magna Graecia.
-
B.
Heraclea at Latmus
Heraclea at Latmus was an ancient Greek city on the coast of Caria in Asia Minor, known for its strategic harbor and proximity to Mount Latmus.
-
C.
Heraclea Lyncestis
Heraclea Lyncestis was an ancient Macedonian city, later a significant Roman and Byzantine center, located near modern Bitola in North Macedonia.
-
D.
Heraklonas
Heraklonas was a short-reigning 7th-century Byzantine emperor, son of Heraclius, whose brief rule was marked by political turmoil and rapid overthrow.
-
E.
Troesmis
Troesmis was an ancient Roman military and urban settlement in the province of Moesia, strategically located near the Danube River in what is now Romania.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8af18e4819091811bca657c9cb0 |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5255f7730819087dc4b10565e321d |
completed | April 19, 2026, 6:56 p.m. |
Created at: April 8, 2026, 9:29 p.m.