Triple
T18200678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beroea |
E435773
|
entity |
| Predicate | greekName |
P3659
|
FINISHED |
| Object | Βέροια |
—
|
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: Βέροια | Statement: [Beroea, greekName, Βέροια]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Βέροια Context triple: [Beroea, greekName, Βέροια]
-
A.
Βέροια
chosen
Βέροια is a historic city in northern Greece, located in Central Macedonia and known for its rich Byzantine heritage and proximity to Mount Vermio.
-
B.
Βύρωνας
Βύρωνας is a suburban municipality of Athens, Greece, known for its dense urban character and proximity to Mount Hymettus.
-
C.
Veroia
Veroia is a historic city in northern Greece, known for its Byzantine churches, Ottoman-era architecture, and proximity to the ancient Macedonian site of Vergina.
-
D.
Volosko
Volosko is a historic coastal village and former fishing port on the Adriatic Sea, now part of the town of Opatija in western Croatia.
-
E.
Borriana
Borriana is a coastal town and municipality in eastern Spain known for its citrus agriculture and Mediterranean beaches.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d610f88190b4f69b1c433ea6b1 |
completed | April 19, 2026, 2:04 p.m. |
Created at: April 10, 2026, 10:31 a.m.