Triple

T3619189
Position Surface form Disambiguated ID Type / Status
Subject Batavian people E76679 entity
Predicate politicalStatusUnderRome P23875 FINISHED
Object client people 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: client people | Statement: [Batavian people, politicalStatusUnderRome, client people]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: politicalStatusUnderRome
Context triple: [Batavian people, politicalStatusUnderRome, client people]
  • A. politicalStatusInAntiquity chosen
    Indicates the political condition or classification an entity held during ancient times, such as its form of governance, sovereignty, or dependency.
  • B. preRomanStatus
    Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
  • C. legalStatusInEmpire
    Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
  • 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. roleInRome
    Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
  • 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_69ad85dae2fc81908d1ceadbc6af0089 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc2b72b3481909f4a09000d1815d9 completed March 8, 2026, 6:40 p.m.
PD Predicate disambiguation batch_69adb83f1e4c8190ab501c1c05b14c08 completed March 8, 2026, 5:56 p.m.
Created at: March 8, 2026, 3:23 p.m.