Triple

T8925304
Position Surface form Disambiguated ID Type / Status
Subject Cohors I Tungrorum E212524 entity
Predicate servedOnFrontier P27674 FINISHED
Object northern frontier of Roman Britain 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: northern frontier of Roman Britain | Statement: [Cohors I Tungrorum, servedOnFrontier, northern frontier of Roman Britain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servedOnFrontier
Context triple: [Cohors I Tungrorum, servedOnFrontier, northern frontier of Roman Britain]
  • A. FrontierStatus
    Indicates the status or condition of something in relation to a boundary, edge, or frontier context (such as being at, beyond, or within that frontier).
  • B. servesOn chosen
    Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
  • C. servedFrom
    Indicates that something is provided, delivered, or made available from a particular source or location.
  • D. wasFrontierRegion
    Indicates that a region historically functioned as a frontier area, marking a boundary or border zone between larger political or cultural entities.
  • E. servedUntil
    Indicates the ending time or date up to which an entity held a position, role, or service.
  • 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_69ca839481d48190b42b037e0d0f636c completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc66700fb48190874563e535f20437 completed April 1, 2026, 12:27 a.m.
PD Predicate disambiguation batch_69cc5ed0ef3c81908cc69eac852ee12a completed March 31, 2026, 11:54 p.m.
Created at: March 30, 2026, 6:57 p.m.