Triple

T32540860
Position Surface form Disambiguated ID Type / Status
Subject Assyrian forces E831707 entity
Predicate usedLogistics P136100 FINISHED
Object royal road system 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: royal road system | Statement: [Assyrian forces, usedLogistics, royal road system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedLogistics
Context triple: [Assyrian forces, usedLogistics, royal road system]
  • A. usedLogisticsRoute chosen
    Indicates that a particular logistics route was employed to transport or move goods or resources between locations.
  • B. logistics
    Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
  • C. logisticsFeature
    Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
  • D. logisticsConcept
    Indicates a conceptual or categorical relationship where one entity represents, defines, or is classified as a logistics-related concept for another entity.
  • E. logisticsSegment
    Indicates a distinct portion or leg of a broader logistics or transportation process that connects two stages in the movement of goods or resources.
  • 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_69f34924b1cc8190ad3aca0c0f012a7e completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c57e3ea48190a075c1165db4eecd completed May 3, 2026, 3:48 a.m.
PD Predicate disambiguation batch_69f6bd2a14b081908162923dfbf0a6f4 completed May 3, 2026, 3:12 a.m.
Created at: May 1, 2026, 1:02 a.m.