Triple

T4411501
Position Surface form Disambiguated ID Type / Status
Subject 442nd Regimental Combat Team E94861 entity
Predicate notableMemberGroup P7128 FINISHED
Object Nisei soldiers 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: Nisei soldiers | Statement: [442nd Regimental Combat Team, notableMemberGroup, Nisei soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableMemberGroup
Context triple: [442nd Regimental Combat Team, notableMemberGroup, Nisei soldiers]
  • A. notableCharacterGroup
    Indicates that a group of characters is especially prominent, significant, or noteworthy within a given context or work.
  • B. notablePersonnel chosen
    Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
  • C. notableMemberNationality
    Indicates that the notable member of a group or organization has the specified nationality.
  • D. hasNotableMember
    Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
  • E. holderNotableFor
    Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
  • 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.