Triple

T1310871
Position Surface form Disambiguated ID Type / Status
Subject Maywood, Illinois E27985 entity
Predicate hasEthnicCharacteristic P27835 FINISHED
Object racially and ethnically diverse community 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: racially and ethnically diverse community | Statement: [Maywood, Illinois, hasEthnicCharacteristic, racially and ethnically diverse community]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEthnicCharacteristic
Context triple: [Maywood, Illinois, hasEthnicCharacteristic, racially and ethnically diverse community]
  • A. affectedEthnicGroup
    Indicates that a particular ethnic group is impacted or influenced by an event, condition, policy, or action.
  • B. ethnicOrigin
    Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
  • C. involvedEthnicGroup
    Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or entity.
  • D. spokenByEthnicGroup
    Indicates that a particular language, dialect, or speech variety is used or spoken by a specified ethnic group.
  • E. otherEthnicGroup
    Indicates that one entity belongs to a different ethnic group than the other entity.
  • F. None of above. chosen

Provenance (4 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_69a496d7d83481908f83085854e51328 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c1560f888190bdd9107b08395e0b completed March 1, 2026, 10:44 p.m.
PD Predicate disambiguation batch_69a4bee9e4a88190b22ab2ee831a23c9 completed March 1, 2026, 10:34 p.m.
PDg Predicate description generation batch_69a4c15361c8819094b8171e780b5560 completed March 1, 2026, 10:44 p.m.
Created at: March 1, 2026, 7:51 p.m.