Triple
T1060889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeotia |
E22903
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Locris |
E72437
|
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: Locris | Statement: [Boeotia, borders, Locris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Locris Context triple: [Boeotia, borders, Locris]
-
A.
Locris
chosen
Locris was an ancient Greek region in central Greece, inhabited by the Locrians and known for its strategic position between Boeotia and Phocis.
-
B.
Phocis
Phocis was an ancient region in central Greece, notable for encompassing the sacred sanctuary and oracle of Delphi.
-
C.
Aetolia
Aetolia is a historical region in western Greece known from ancient times for its rugged terrain and role in Greek history and mythology.
-
D.
Thessaly
Thessaly is a historical and geographical region in central Greece known for its fertile plains, ancient cities, and proximity to landmarks like Mount Olympus and Meteora.
-
E.
Argolid
Argolid is a historic region in the northeastern Peloponnese of Greece, renowned as the heartland of several major Bronze Age and classical Greek centers.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f3f98c819096338198d9f30491 |
completed | March 1, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad0e5bc6348190a0d23fe269707e1b |
completed | March 8, 2026, 5:51 a.m. |
Created at: March 1, 2026, 7:42 p.m.