Triple

T29698238
Position Surface form Disambiguated ID Type / Status
Subject Beijing area E751409 entity
Predicate historicalPredecessorRole P29914 FINISHED
Object capital region of several Chinese dynasties 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: capital region of several Chinese dynasties | Statement: [Beijing area, historicalPredecessorRole, capital region of several Chinese dynasties]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalPredecessorRole
Context triple: [Beijing area, historicalPredecessorRole, capital region of several Chinese dynasties]
  • A. hasHistoricalRoleAs chosen
    Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
  • B. historicalEntityPredecessor
    Indicates that one historical entity existed or held a role before another, serving as its predecessor in time or sequence.
  • C. predecessorInRole
    Indicates that one entity previously held a particular role or position that was later occupied by another entity.
  • D. hasNamesakeRoleInHistory
    Indicates that an entity has a historical role or position that is the same as, or named after, another entity’s role in history.
  • E. roleHistoricallyAssociatedWith
    Indicates that one role, position, or function has been historically linked or commonly associated with another entity, role, or context over 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_69f0d6266f8481909e70bb41cda18587 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fe9dfaa2d08190b2084f63f842eb6b completed May 9, 2026, 2:37 a.m.
PD Predicate disambiguation batch_69fe9bba947c81908b0b2b92a4d19b37 completed May 9, 2026, 2:28 a.m.
Created at: April 28, 2026, 7:22 p.m.