Triple

T50686
Position Surface form Disambiguated ID Type / Status
Subject Dutch East Indies E993 entity
Predicate ethnicGroups P1898 FINISHED
Object Javanese 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: Javanese | Statement: [Dutch East Indies, ethnicGroups, Javanese]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ethnicGroups
Context triple: [Dutch East Indies, ethnicGroups, Javanese]
  • A. relatedEthnicGroup
    Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
  • B. hasSignificantPopulationGroup chosen
    Indicates that an entity contains or is associated with a notable or substantial subgroup of a population, distinguished by shared characteristics or attributes.
  • C. ethnicOrigin
    Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
  • D. culturalRegion
    Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
  • E. demographics
    Indicates the relationship of providing or characterizing statistical information about a population’s attributes, such as age, gender, income, or education.
  • 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_69a2480baefc81909951b14058479aa2 completed Feb. 28, 2026, 1:42 a.m.
NER Named-entity recognition batch_69a24ba7016481909d595402712db6e2 completed Feb. 28, 2026, 1:57 a.m.
PD Predicate disambiguation batch_69a24ac23f04819080cef9365ed990d4 completed Feb. 28, 2026, 1:54 a.m.
Created at: Feb. 28, 2026, 1:47 a.m.