Triple

T4411438
Position Surface form Disambiguated ID Type / Status
Subject Korematsu v. United States E94860 entity
Predicate raceClassification P18104 FINISHED
Object Japanese ancestry 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: Japanese ancestry | Statement: [Korematsu v. United States, raceClassification, Japanese ancestry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: raceClassification
Context triple: [Korematsu v. United States, raceClassification, Japanese ancestry]
  • A. raceCategory chosen
    Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
  • B. stageRaceType
    Indicates the specific category or format of a multi-stage race within a broader competition or event.
  • C. competitionClass
    Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
  • D. speedClass
    Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
  • E. raceStatus
    Indicates the current state or progress of an entity’s participation in a race or competitive event.
  • 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_69b34539638c8190abfea3eb29425210 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b354e656dc819093ca8395d7334006 completed March 13, 2026, 12:05 a.m.
PD Predicate disambiguation batch_69b34f5b36a881909bf2e970aa523390 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:29 p.m.