Triple

T1656017
Position Surface form Disambiguated ID Type / Status
Subject British monarchy E35800 entity
Predicate unifiedInCurrentForm P763 FINISHED
Object 1922 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: 1922 | Statement: [British monarchy, unifiedInCurrentForm, 1922]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: unifiedInCurrentForm
Context triple: [British monarchy, unifiedInCurrentForm, 1922]
  • A. establishedInCurrentForm chosen
    Indicates the point in time when something took on its present structure, organization, or configuration, distinct from any earlier versions or forms.
  • B. establishedInCurrentFormBy
    Indicates that one entity created, organized, or defined another entity in the specific structure or configuration in which it currently exists.
  • C. standardFormBasedOn
    Indicates that one entity’s standard or canonical form is derived from, defined by, or constructed on the basis of another entity.
  • D. usesForm
    Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
  • E. unificationPossible
    Indicates that two entities can be combined or reconciled into a single, consistent representation under a shared set of constraints or rules.
  • 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_69a88606aa808190aa0b421b4271f220 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aaf3359ce48190803b322db8ad6027 completed March 6, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69a907cff53c8190b424f088478d3e2c completed March 5, 2026, 4:34 a.m.
Created at: March 4, 2026, 7:29 p.m.