Triple
T33918246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Council of La Raza |
E869526
|
entity |
| Predicate | changeNameReason |
P2136
|
FINISHED |
| Object | to adopt a more inclusive and contemporary identity |
—
|
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: to adopt a more inclusive and contemporary identity | Statement: [National Council of La Raza, changeNameReason, to adopt a more inclusive and contemporary identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeNameReason Context triple: [National Council of La Raza, changeNameReason, to adopt a more inclusive and contemporary identity]
-
A.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
B.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
C.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
D.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
E.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:49 a.m.