Triple
T33063398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogharun |
E846031
|
entity |
| Predicate | borderCrossesWith |
P13760
|
FINISHED |
| Object | Afghanistan |
—
|
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: Afghanistan | Statement: [Dogharun, borderCrossesWith, Afghanistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossesWith Context triple: [Dogharun, borderCrossesWith, Afghanistan]
-
A.
crossesBorderOf
chosen
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
crossedBoundary
Indicates that an entity has moved from one defined area, region, or limit into another, thereby passing across a specified boundary.
-
D.
borderStraddling
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
E.
borderCrossingArea
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
- F. None of above.
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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: May 1, 2026, 1:25 a.m.