Triple
T34911860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerto Rico Highway 118 |
E1006891
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Puerto Rico |
C58129
|
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 Puerto Rico Context triple: [Puerto Rico Highway 118, instanceOf, road in Puerto Rico]
-
A.
Puerto Rico highway
chosen
A Puerto Rico highway is a numbered public road within the Puerto Rico highway and transportation network designed to facilitate vehicular travel between municipalities, regions, and key destinations across the island.
-
B.
street in San Juan, Puerto Rico
A street in San Juan, Puerto Rico is a public urban thoroughfare within the city’s historic or modern districts, lined with local residences, businesses, and cultural landmarks that facilitate vehicular and pedestrian movement.
-
C.
road in Costa Rica
A road in Costa Rica is a public transportation route, often varying from paved highways to unpaved rural paths, that connects towns, cities, and natural areas across the country’s diverse terrain.
-
D.
road in Guam
A road in Guam is a paved or unpaved transportation route on the island that connects towns, villages, and key locations, accommodating vehicles and sometimes pedestrians within Guam’s tropical, coastal, and often hilly terrain.
-
E.
road in Jamaica
A road in Jamaica is a paved or unpaved transportation route that connects towns, cities, and rural areas across the island, accommodating vehicles, pedestrians, and local traffic within Jamaica’s tropical environment and cultural context.
- F. None of above.
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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.