Triple

T37944783
Position Surface form Disambiguated ID Type / Status
Subject Busra al-Sham E946575 entity
Predicate onAncientRoute P102051 FINISHED
Object trade routes between Arabia and Damascus LITERAL FINISHED

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: trade routes between Arabia and Damascus | Statement: [Busra al-Sham, onAncientRoute, trade routes between Arabia and Damascus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: onAncientRoute
Context triple: [Busra al-Sham, onAncientRoute, trade routes between Arabia and Damascus]
  • A. transportRouteInAntiquity chosen
    Indicates that there existed a transportation route between entities during ancient or classical historical periods.
  • B. isAncient
    Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
  • C. nearHistoricalRoute
    Indicates that one entity is located close to a historically significant route or pathway.
  • D. usesFormerRouteOf
    Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
  • E. historicalRouteName
    Indicates that an entity has or is associated with a name it held historically as a route or pathway, distinct from its current official name.
  • 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_69f76ef531ac8190ae6d99e5786e76ec completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc7b78f9481909f4f8fc2e3fdcde1 completed May 6, 2026, 10:59 p.m.
PD Predicate disambiguation batch_69fbbd18c9908190928d274f8731dfa8 completed May 6, 2026, 10:13 p.m.
Created at: May 3, 2026, 4:20 p.m.