Triple
T33486709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagratashen–Sadakhlo border crossing |
E857631
|
entity |
| Predicate | locatedOnGeorgianSideIn |
P206489
|
FINISHED |
| Object | Sadakhlo |
E2053587
|
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: Sadakhlo | Statement: [Bagratashen–Sadakhlo border crossing, locatedOnGeorgianSideIn, Sadakhlo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnGeorgianSideIn Context triple: [Bagratashen–Sadakhlo border crossing, locatedOnGeorgianSideIn, Sadakhlo]
-
A.
locatedOnSideOfGreekMainland
Indicates that one place is situated on the side of the Greek mainland relative to another reference point or area.
-
B.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
C.
locatedOnPeninsula
Indicates that one entity is situated on or within the geographic area of a peninsula.
-
D.
locatedInBritishCountry
Indicates that one entity is geographically or administratively situated within a country that is part of the United Kingdom.
-
E.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
- F. None of above. chosen
Provenance (5 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35a66a65e081908086b523783265d2 |
completed | June 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:38 a.m.