Triple

T3368416
Position Surface form Disambiguated ID Type / Status
Subject Picenum E70891 entity
Predicate preRomanPoliticalStructure P12864 FINISHED
Object tribal communities 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: tribal communities | Statement: [Picenum, preRomanPoliticalStructure, tribal communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: preRomanPoliticalStructure
Context triple: [Picenum, preRomanPoliticalStructure, tribal communities]
  • A. preRomanStatus chosen
    Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
  • B. preMonarchicGovernment
    Indicates that an entity has a form of government that existed before the establishment of a monarchy.
  • C. precolonialPolity
    Indicates that an entity functioned as a political or governing unit during the period before colonial rule was established in its region.
  • D. RomanRepresentative
    Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
  • E. governedInAntiquityBy
    Indicates that one entity exercised political rule or authority over another entity during ancient or classical historical periods.
  • 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_69ad85a729d48190afd789cd8417f289 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb28a813c81909d1c71fe577e6681 completed March 8, 2026, 5:31 p.m.
PD Predicate disambiguation batch_69ada4317e288190ab7d0f66e9dba65f completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:13 p.m.