Triple

T24244741
Position Surface form Disambiguated ID Type / Status
Subject Hertevin E603331 entity
Predicate vernacularType P5302 FINISHED
Object rural village vernacular 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: rural village vernacular | Statement: [Hertevin, vernacularType, rural village vernacular]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vernacularType
Context triple: [Hertevin, vernacularType, rural village vernacular]
  • A. vernacularOf
    Indicates that one language or dialect is the everyday, locally used form corresponding to another, more general or standard language.
  • B. vernacularGroup
    Indicates a relationship where entities are grouped or associated based on sharing the same vernacular (local or commonly spoken) language.
  • C. linguisticType chosen
    Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
  • D. linguisticVariant
    Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
  • E. vernacularLanguagePeriod
    Indicates the time span during which a particular vernacular (locally spoken) language was in use or predominant in a given context.
  • 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_69e2953f631c819097cbb421046bd417 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28b82e13c819083ca524e47ed66b1 completed April 29, 2026, 10:51 p.m.
PD Predicate disambiguation batch_69f1c448abec8190b87cbf9ed419a309 completed April 29, 2026, 8:41 a.m.
Created at: April 18, 2026, 12:04 a.m.