Triple

T28119197
Position Surface form Disambiguated ID Type / Status
Subject Legio II Augusta E710728 entity
Predicate roleInBoudicanRevolt P88009 FINISHED
Object part of forces that suppressed the revolt 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: part of forces that suppressed the revolt | Statement: [Legio II Augusta, roleInBoudicanRevolt, part of forces that suppressed the revolt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInBoudicanRevolt
Context triple: [Legio II Augusta, roleInBoudicanRevolt, part of forces that suppressed the revolt]
  • A. roleInGallicWars
    Indicates the role or involvement an entity had in the events or campaigns of the Gallic Wars.
  • B. roleInNoricum
    Indicates that an entity holds or held a specific role, position, or function within the historical region or province of Noricum.
  • C. roleUnderCarausius
    Indicates that one entity held a role, position, or office subordinate to or under the authority of Carausius.
  • D. roleInRevolt chosen
    Indicates the specific function, position, or level of participation an entity had within a particular revolt or uprising.
  • E. roleInRaetia
    Indicates that an entity held a specific role, position, or function within the Roman province of Raetia.
  • 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_69ef9b72f63081909dfbc2c1ddae86c6 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69fddf721c1481909301a0f379368f10 completed May 8, 2026, 1:04 p.m.
PD Predicate disambiguation batch_69fddda1ae7c8190b5848ff9a9e39826 completed May 8, 2026, 12:57 p.m.
Created at: April 27, 2026, 9:16 p.m.