Triple

T33290790
Position Surface form Disambiguated ID Type / Status
Subject Cobá road network E852313 entity
Predicate instanceOf P0 FINISHED
Object ancient transportation network C1081 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: ancient transportation network
Context triple: [Cobá road network, instanceOf, ancient transportation network]
  • A. ancient trade route
    An ancient trade route is a historically established pathway or network used for the long-distance exchange of goods, ideas, cultures, and technologies between regions and civilizations.
  • B. historic transportation system chosen
    A historic transportation system is an organized network of vehicles, routes, and infrastructure from a past era that once facilitated the movement of people or goods and is now preserved, studied, or remembered for its cultural, technological, or historical significance.
  • C. Inca road system
    The Inca road system was an extensive, sophisticated network of paved and unpaved routes spanning thousands of kilometers across the Andes, designed to connect and administer the vast Inca Empire through efficient communication, trade, and military movement.
  • D. transport infrastructure network
    A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
  • E. ancient route listing
    An ancient route listing is a documented catalog of historical travel paths, roads, or trade routes, often detailing their locations, connections, and significance in past civilizations.
  • 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_69f349660ff48190a4568803d0b89941 completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:32 a.m.