Triple

T28880968
Position Surface form Disambiguated ID Type / Status
Subject Menua Canal E732414 entity
Predicate builtByCulture P76641 FINISHED
Object Urartian Kingdom 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: Urartian Kingdom | Statement: [Menua Canal, builtByCulture, Urartian Kingdom]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: builtByCulture
Context triple: [Menua Canal, builtByCulture, Urartian Kingdom]
  • A. developedByCulture chosen
    Indicates that something (such as a practice, artifact, or idea) has been created, shaped, or brought into being through the influence or processes of a particular culture.
  • B. writtenByCulture
    Indicates that something (such as a text, work, or artifact) is authored, created, or produced by a particular culture or cultural group.
  • C. basedInCulture
    Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
  • D. hasCulturalLegacyIn
    Indicates that an entity has left a lasting cultural influence, impact, or heritage within a particular place, community, or cultural context.
  • E. introducedCulture
    Indicates that one entity brought or established a particular culture within another entity, context, or environment.
  • 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_69f05b07bdec819080cadfe147aa1f25 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f65a6d639481909e661755a5838a47 completed May 2, 2026, 8:11 p.m.
PD Predicate disambiguation batch_69f65762b5e481908a30ca963dcba4be completed May 2, 2026, 7:58 p.m.
Created at: April 28, 2026, 7:44 a.m.