Triple

T8227399
Position Surface form Disambiguated ID Type / Status
Subject Campaigns in Armorica E192205 entity
Predicate militaryTacticUsedByRomans P30685 FINISHED
Object naval blockade 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: naval blockade | Statement: [Campaigns in Armorica, militaryTacticUsedByRomans, naval blockade]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryTacticUsedByRomans
Context triple: [Campaigns in Armorica, militaryTacticUsedByRomans, naval blockade]
  • A. militaryTacticsUsed chosen
    Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
  • B. militaryContributionToRome
    Indicates that an entity provides military forces, support, or resources in service of or on behalf of Rome.
  • C. estimatedRomanForces
    Indicates that a specified quantity represents an estimate of the size or strength of Roman military forces involved in a particular context or event.
  • D. militaryTacticsFaced
    Indicates that an entity encountered or had to contend with specific military tactics employed by another entity.
  • E. usedInRomanPeriodFor
    Indicates that something served a particular function, purpose, or application during the Roman period.
  • 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_69ca82db5b90819085d1ad7c2e27bfcc completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb77fdcb048190868ea4995b020a37 completed March 31, 2026, 7:30 a.m.
PD Predicate disambiguation batch_69cb36af41e081909dee92b9bc4947f1 completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:46 p.m.