Triple

T16734003
Position Surface form Disambiguated ID Type / Status
Subject A10 road E406669 entity
Predicate historicallyFollows P16345 FINISHED
Object route of Roman Ermine Street in parts 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 of Roman Ermine Street in parts | Statement: [A10 road, historicallyFollows, route of Roman Ermine Street in parts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyFollows
Context triple: [A10 road, historicallyFollows, route of Roman Ermine Street in parts]
  • A. historicallyExtendedBy
    Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
  • B. historicallyLinked chosen
    Indicates that two entities are connected through a shared or related historical event, period, or development.
  • C. followsBy
    Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
  • D. followsTo
    Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
  • E. heritageFollowedBy
    Indicates that one heritage, tradition, or cultural lineage comes after and is influenced or continued by another in a temporal or developmental sequence.
  • 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e39c38c9cc8190a3220cc3684388dc completed April 18, 2026, 2:59 p.m.
PD Predicate disambiguation batch_69e319c807788190901250ab6e0ca55f completed April 18, 2026, 5:42 a.m.
Created at: April 10, 2026, 5:20 a.m.