Triple
T11494783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beit Hanina |
E272505
|
entity |
| Predicate | hasRoadConnection |
P385
|
FINISHED |
| Object | Route 60 |
E803552
|
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: Route 60 | Statement: [Beit Hanina, hasRoadConnection, Route 60]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Route 60 Context triple: [Beit Hanina, hasRoadConnection, Route 60]
-
A.
Route 60
Route 60 is a major east–west freeway in Southern California that serves as a key commuter and freight corridor through the Inland Empire and Greater Los Angeles region.
-
B.
Route 60
chosen
Route 60 is a major north–south highway in Israel and the West Bank that connects key cities including Jerusalem, Hebron, and Nablus.
-
C.
Route 62
Route 62 is a regional roadway that serves as a key connector through parts of Massachusetts, including the area near West Concord.
-
D.
Route 64
Route 64 is a Chilean roadway that serves as a key regional connector in the Valparaíso area, linking the inland city of Quilpué with surrounding localities and major routes.
-
E.
Route 606
Route 606 is a highway that serves as a key transportation link to the Afghan border city of Zaranj.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de183f08190abfa36eaabc61dc6 |
completed | April 10, 2026, 2:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6048a05c88190968f7827c5dd5342 |
completed | April 20, 2026, 10:48 a.m. |
Created at: April 8, 2026, 9:36 p.m.