Triple
T37431481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highway 75 (Israel) |
E930148
|
entity |
| Predicate | majorRoadwayIn |
P29360
|
FINISHED |
| Object | northern Israel |
—
|
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: northern Israel | Statement: [Highway 75 (Israel), majorRoadwayIn, northern Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRoadwayIn Context triple: [Highway 75 (Israel), majorRoadwayIn, northern Israel]
-
A.
isMajorRoadIn
chosen
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
B.
mainRoadInfrastructure
Indicates that a road segment functions as a primary or major route within the transportation infrastructure network.
-
C.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
-
D.
majorTransportCorridor
Indicates that a route or pathway functions as a primary, high-capacity channel for transporting people or goods between significant locations.
-
E.
isMajorCommercialStreetOf
Indicates that a street serves as a primary, heavily used route for commercial activity within a specified area or locality.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 3, 2026, 4:17 p.m.