Triple
T37700331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engineer Lane |
E939040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Gibraltar |
C65227
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: road in Gibraltar Context triple: [Engineer Lane, instanceOf, road in Gibraltar]
-
A.
road in Spain
A road in Spain is a public thoroughfare within Spanish territory, ranging from local streets to national highways, designed for vehicular and pedestrian transit under Spain’s traffic and infrastructure regulations.
-
B.
road in Morocco
A road in Morocco is a transportation route that connects cities, towns, and rural areas across diverse landscapes—from coastal plains and deserts to mountain passes—facilitating movement of people, goods, and services within the country.
-
C.
road in the United Kingdom
A road in the United Kingdom is a public or private thoroughfare designed for vehicular and pedestrian travel, classified and regulated according to national standards such as motorways, A-roads, B-roads, and local streets.
-
D.
A road in Great Britain
A road in Great Britain is a public or private vehicular thoroughfare, classified and maintained under UK transport regulations, that connects places and supports the movement of people and goods across the country.
-
E.
road in Portugal
A road in Portugal is a designated transportation route within Portuguese territory, ranging from local streets to national highways, that facilitates vehicular and pedestrian movement while adhering to the country’s traffic regulations and infrastructure standards.
- F. None of above. chosen
Provenance (1 batch)
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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.