Triple

T190487
Position Surface form Disambiguated ID Type / Status
Subject Lower Egypt E3708 entity
Predicate languageInAntiquity P1434 FINISHED
Object Egyptian language 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: Egyptian language | Statement: [Lower Egypt, languageInAntiquity, Egyptian language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageInAntiquity
Context triple: [Lower Egypt, languageInAntiquity, Egyptian language]
  • A. languageOfEarliestForm
    Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
  • B. hasWritingTraditionSince
    Indicates that a writing tradition has been present or established for an entity starting from a specified point in time.
  • C. literaryTradition
    Indicates a relationship where a work, practice, or expression belongs to, arises from, or participates in a particular established body of literary customs, styles, or conventions.
  • D. historicallySpokenIn chosen
    Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
  • E. hasLanguageOfScripture
    Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
  • 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_69a2548debd48190ae3a06d6e65b53c6 completed Feb. 28, 2026, 2:35 a.m.
NER Named-entity recognition batch_69a2594c385481909e1e088e45c460a4 completed Feb. 28, 2026, 2:56 a.m.
PD Predicate disambiguation batch_69a25673ce3c8190b1a3df5b814a0595 completed Feb. 28, 2026, 2:44 a.m.
Created at: Feb. 28, 2026, 2:41 a.m.