Triple

T6466809
Position Surface form Disambiguated ID Type / Status
Subject Deir Alla dialect E142251 entity
Predicate hasCorpusStatus P18537 FINISHED
Object known only from inscriptions 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: known only from inscriptions | Statement: [Deir Alla dialect, hasCorpusStatus, known only from inscriptions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCorpusStatus
Context triple: [Deir Alla dialect, hasCorpusStatus, known only from inscriptions]
  • A. hasCorpusType
    Indicates the type or category of corpus associated with an entity (e.g., text, speech, multimodal).
  • B. hasPartOfCorpus
    Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
  • C. hasNotableCorpus
    Indicates that an entity possesses a significant, well-recognized body of work, texts, or collected materials associated with it.
  • D. hasDocumentationStatus
    Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
  • E. hasLimitedCorpus chosen
    Indicates that the associated entity possesses only a small or restricted set of available data, texts, or examples for use or analysis.
  • 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_69c008d3bf4c8190bcf798c5ba9d6fb3 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06a12ccf481908f71f888cd744b64 completed March 22, 2026, 10:15 p.m.
PD Predicate disambiguation batch_69c0673d46a08190bc8bcd29f9555fe7 completed March 22, 2026, 10:03 p.m.
Created at: March 22, 2026, 4:49 p.m.