Triple
T26027165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | מכתש רמון |
E647323
|
entity |
| Predicate | נגיש דרך |
P9041
|
FINISHED |
| Object | כביש 40 |
—
|
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: כביש 40 | Statement: [מכתש רמון, נגיש דרך, כביש 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: נגיש דרך Context triple: [מכתש רמון, נגיש דרך, כביש 40]
-
A.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
B.
roadAccessVia
chosen
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
C.
보급 경로
Indicates the route or pathway through which supplies or provisions are delivered or distributed from their source to their intended recipients.
-
D.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
E.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605ec65448190895219d85eb0d6a8 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 9:05 a.m.