Triple
T14738420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byala Bridge |
E346276
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Byala |
E340235
|
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: Byala | Statement: [Byala Bridge, locatedIn, Byala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Byala Context triple: [Byala Bridge, locatedIn, Byala]
-
A.
Byala
chosen
Byala is a Bulgarian town situated along the Yantra River, known for its historic bridge and regional administrative role.
-
B.
Barya
Barya is an alternative name for the Nara people, an ethnic group primarily inhabiting parts of Eritrea.
-
C.
Balya
Balya is a small town and district in western Turkey known historically for its mining activities and rural character.
-
D.
Gialova
Gialova is a small coastal village in Messenia, Greece, known for its scenic bay, wetlands, and proximity to historical and natural attractions such as Navarino Bay and Voidokilia Beach.
-
E.
Ballana
Ballana is an important archaeological site in Lower Nubia known for its rich group of royal tumulus graves from the post-Meroitic period.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec73264848190be23c5f0260cbe13 |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb90378481909a3083680f11101c |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.