Triple

T17563792
Position Surface form Disambiguated ID Type / Status
Subject Perusia E427756 entity
Predicate politicalStatusInRomanPeriod P63218 FINISHED
Object municipium 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: municipium | Statement: [Perusia, politicalStatusInRomanPeriod, municipium]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: politicalStatusInRomanPeriod
Context triple: [Perusia, politicalStatusInRomanPeriod, municipium]
  • A. politicalStatusInAntiquity
    Indicates the political condition or classification an entity held during ancient times, such as its form of governance, sovereignty, or dependency.
  • B. RomanRepresentative
    Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
  • C. roleInRome
    Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
  • D. romanStatus chosen
    Indicates the status or condition of an entity within a Roman-specific context, such as its legal, social, or civic standing in Roman society.
  • E. preRomanStatus
    Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
  • 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4592bde448190bf5ed2340440e2b7 completed April 19, 2026, 4:25 a.m.
PD Predicate disambiguation batch_69e3b4fd7d048190b54ee4c6155612a5 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:50 a.m.