Triple

T3442136
Position Surface form Disambiguated ID Type / Status
Subject Eastphalian E72588 entity
Predicate languageCodeStatus P6525 FINISHED
Object no separate ISO 639-3 code (grouped under Low German) 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: no separate ISO 639-3 code (grouped under Low German) | Statement: [Eastphalian, languageCodeStatus, no separate ISO 639-3 code (grouped under Low German)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageCodeStatus
Context triple: [Eastphalian, languageCodeStatus, no separate ISO 639-3 code (grouped under Low German)]
  • A. languageStatusSource
    Indicates the source or authority from which the information about a language’s status is derived.
  • B. ISO639Status
    Indicates the classification of a language’s status according to the ISO 639 standard (e.g., whether and how it is recognized or coded in that system).
  • C. hasLanguageStatus
    Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
  • D. ISO639_3Status chosen
    Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
  • E. languageCodeStandard
    Indicates that a language code conforms to a specific standardized coding scheme (such as ISO language code standards).
  • 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_69ad85af50288190a854b76653deee6f completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adba28ec448190a6a07c5f16235fe3 completed March 8, 2026, 6:04 p.m.
PD Predicate disambiguation batch_69adae0255b48190a9069f7871c7a012 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:16 p.m.