Triple

T10251276
Position Surface form Disambiguated ID Type / Status
Subject Brigantium E240346 entity
Predicate wasSignificantAs P24342 FINISHED
Object regional center in Raetia 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: regional center in Raetia | Statement: [Brigantium, wasSignificantAs, regional center in Raetia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasSignificantAs
Context triple: [Brigantium, wasSignificantAs, regional center in Raetia]
  • A. hasSignificant
    Indicates that one entity possesses or exhibits a level of importance, impact, or relevance that is notably large or meaningful in relation to another entity or context.
  • B. wasA chosen
    Indicates that an entity previously had a certain role, type, or classification in the past.
  • C. significantAfter
    Indicates that one event or state occurs after another in a way that is temporally meaningful or non-trivially later, not just immediately or insignificantly afterward.
  • D. isGloballySignificant
    Indicates that something has importance, impact, or relevance on a worldwide scale rather than being limited to a local or regional context.
  • E. hasParticularSignificanceFor
    Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
  • 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_69d381a7e198819090280d5ab885d59e completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d328272c8190a3548d7f7f38cfc4 completed April 7, 2026, 9:49 a.m.
PD Predicate disambiguation batch_69d4d1ebd6c88190a1f3f4a72a99d6fe completed April 7, 2026, 9:44 a.m.
Created at: April 6, 2026, 11:29 a.m.