Triple

T21604480
Position Surface form Disambiguated ID Type / Status
Subject King of Kent E533132 entity
Predicate hasDynasty P7426 FINISHED
Object Oiscingas NE NERFINISHED

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: Oiscingas | Statement: [King of Kent, hasDynasty, Oiscingas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oiscingas
Context triple: [King of Kent, hasDynasty, Oiscingas]
  • A. Oiscingas chosen
    The Oiscingas were the ruling royal dynasty of early medieval Kent, traditionally descended from the legendary founder Oisc.
  • B. Sangalhos
    Sangalhos is a civil parish in the municipality of Anadia, located in Portugal’s Aveiro District and known for its wine production and local sports traditions.
  • C. Pojulu
    Pojulu are an ethnic group of South Sudan, primarily inhabiting parts of Central Equatoria and speaking a Bari-related Nilotic language.
  • D. Papingo
    Papingo is a picturesque traditional village in the Zagori region of Epirus, northwestern Greece, known for its stone architecture and dramatic mountain scenery.
  • E. Tratarasa
    Tratarasa is an epithet meaning “Saviour King” used on the coins of the Indo-Greek ruler Apollodotus I.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46364608190a337dc8720dc2a35 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef17e3e18c8190b9e0626c7d16805b completed April 27, 2026, 8:01 a.m.
Created at: April 16, 2026, 6:33 p.m.