Triple

T32028944
Position Surface form Disambiguated ID Type / Status
Subject Marcomannic kingdom in Bohemia E817894 entity
Predicate statusRelativeToRome P87817 FINISHED
Object formally recognized as a client kingdom 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: formally recognized as a client kingdom | Statement: [Marcomannic kingdom in Bohemia, statusRelativeToRome, formally recognized as a client kingdom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusRelativeToRome
Context triple: [Marcomannic kingdom in Bohemia, statusRelativeToRome, formally recognized as a client kingdom]
  • A. laterRelationToRome
    Indicates that one entity occurs or exists at a time later than the reference time associated with Rome.
  • B. significanceToRome
    Indicates that something holds particular importance, influence, or relevance in relation to Rome.
  • C. stanceTowardRome
    Indicates the nature or attitude of an entity’s position or policy in relation to Rome.
  • D. consideredByRomeAs chosen
    Indicates that something or someone is regarded or classified in a particular way by Rome (e.g., Roman authorities, culture, or legal system).
  • E. statusRelativeTo
    Indicates the comparative state or condition of one entity in relation to another at a given point or over a period of time.
  • 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_69f348fb04e4819081f4eab040ed7959 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fe78e545888190a239af1a84280fa0 completed May 8, 2026, 11:59 p.m.
PD Predicate disambiguation batch_69fe7842742081908043eb950ed69f92 completed May 8, 2026, 11:56 p.m.
Created at: May 1, 2026, 12:17 a.m.