Triple

T2397599
Position Surface form Disambiguated ID Type / Status
Subject Tarsus E47685 entity
Predicate onTradeRoute P35626 FINISHED
Object route between Syria and central Anatolia 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: route between Syria and central Anatolia | Statement: [Tarsus, onTradeRoute, route between Syria and central Anatolia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: onTradeRoute
Context triple: [Tarsus, onTradeRoute, route between Syria and central Anatolia]
  • A. includesTradeRoute chosen
    Indicates that one entity contains, encompasses, or makes use of a particular trade route within its scope or structure.
  • B. tradeSystem
    Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
  • C. trades
    Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
  • D. tradesAs
    Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
  • E. tradeNetwork
    Indicates a relationship where entities are connected through the exchange of goods, services, or resources within an ongoing system of trade.
  • 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_69a88a1c450c81909f61abb8b6863885 completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abc8c5f0948190b4ea729693d8c306 completed March 7, 2026, 6:42 a.m.
PD Predicate disambiguation batch_69abc5a3825c81909ec6111dfc165453 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:57 p.m.