Triple

T4731831
Position Surface form Disambiguated ID Type / Status
Subject Principality of Serbia E105026 entity
Predicate autonomyRecognizedByOttomanEmpire P5083 FINISHED
Object 1830 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: 1830 | Statement: [Principality of Serbia, autonomyRecognizedByOttomanEmpire, 1830]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: autonomyRecognizedByOttomanEmpire
Context triple: [Principality of Serbia, autonomyRecognizedByOttomanEmpire, 1830]
  • A. underOttomanRuleFrom
    Indicates that one entity was under the political authority or control of the Ottoman Empire starting from a specified time.
  • B. OttomanRole
    Indicates that an entity holds or held a specific role, position, or function within the Ottoman Empire.
  • C. wasOttomanCity
    Indicates that a location previously functioned as a city within the territorial or administrative domain of the Ottoman Empire.
  • D. grantsOfAutonomy chosen
    Indicates that one entity confers a degree of self-governance, independence, or decision-making authority to another entity.
  • E. protectorateEstablishedBy
    Indicates that a protectorate relationship was formally created or instituted by a particular actor or authority.
  • 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_69bd43ee52048190b81a4f066534ffb3 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd67c9c3c08190a6c4944cdd1362a8 completed March 20, 2026, 3:29 p.m.
PD Predicate disambiguation batch_69bd6220071881909670c89d072ffb6d completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:19 p.m.