Triple

T311329
Position Surface form Disambiguated ID Type / Status
Subject Venetic language E7613 entity
Predicate iso639-3 P8719 FINISHED
Object xve 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: xve | Statement: [Venetic language, iso639-3, xve]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: iso639-3
Context triple: [Venetic language, iso639-3, xve]
  • A. ISO639_3Status
    Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
  • B. languageCodeISO639-2
    Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
  • C. languageCodeISO639-1
    Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
  • D. hasISO6393Code chosen
    Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
  • E. languageFamilyCode
    Indicates the language family to which a given language belongs, represented by a standardized code.
  • 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_69a2e7e7af7881908890039d6be4e9b8 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ea49636c8190a69cbd951fc0a4db completed Feb. 28, 2026, 1:14 p.m.
PD Predicate disambiguation batch_69a2e940b9e8819092b821ff17ed026b completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:07 p.m.