Triple

T30320067
Position Surface form Disambiguated ID Type / Status
Subject Second Dynasty of Kish E771173 entity
Predicate hasHistoricalDiscipline P76319 FINISHED
Object Assyriology 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: Assyriology | Statement: [Second Dynasty of Kish, hasHistoricalDiscipline, Assyriology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalDiscipline
Context triple: [Second Dynasty of Kish, hasHistoricalDiscipline, Assyriology]
  • A. historicalDiscipline chosen
    Indicates that one entity is a field or branch of academic study within the broader domain of history in relation to another entity.
  • B. hasHistoricalContext
    Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
  • C. historicalSpecialization
    Indicates a relationship where an entity’s expertise, role, or function is specifically focused on a particular historical period, theme, or subject.
  • D. hasHistoricalSection
    Indicates that something includes a dedicated part or segment that presents historical information or context.
  • E. hasResearchHistory
    Indicates that an entity has a documented record of past research activities, projects, or studies.
  • 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_69f22489ee8481909344649bfbb92e83 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fda94697c4819081291967202248be completed May 8, 2026, 9:13 a.m.
PD Predicate disambiguation batch_69fda5973fcc8190a57daef31fb70a49 completed May 8, 2026, 8:57 a.m.
Created at: April 29, 2026, 7:52 p.m.