Triple
T33486718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagratashen–Sadakhlo border crossing |
E857631
|
entity |
| Predicate | connectsRoadNetworkOf |
P176401
|
FINISHED |
| Object | Armenia |
—
|
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: Armenia | Statement: [Bagratashen–Sadakhlo border crossing, connectsRoadNetworkOf, Armenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsRoadNetworkOf Context triple: [Bagratashen–Sadakhlo border crossing, connectsRoadNetworkOf, Armenia]
-
A.
connectsRoadNetwork
Indicates that one entity is linked to another as part of the same road network, enabling continuous vehicular or transport connectivity between them.
-
B.
linksToRoadNetwork
chosen
Indicates that an entity is connected or provides access to a road network.
-
C.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
D.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
E.
streetNetwork
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: May 1, 2026, 1:38 a.m.