Triple

T34065850
Position Surface form Disambiguated ID Type / Status
Subject Cesar Chavez Street E873618 entity
Predicate namedForEponymNotability P124100 FINISHED
Object civil rights activism 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: civil rights activism | Statement: [Cesar Chavez Street, namedForEponymNotability, civil rights activism]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: namedForEponymNotability
Context triple: [Cesar Chavez Street, namedForEponymNotability, civil rights activism]
  • A. hasEponymNotability
    Indicates that an entity is notable specifically for having something (such as a place, object, or concept) named after it.
  • B. namedForNotabilityOfHonoree chosen
    Indicates that something is named in recognition of the honoree’s notable achievements, status, or significance.
  • C. nameTypeNotability
    Indicates that the type or category of a name is determined or influenced by the notability or prominence associated with it.
  • D. isNamedForEponymRole
    Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
  • E. hasNamesakeNotability
    Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
  • 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_69f349a4af208190afa14888f9c9fb9d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fccdd496048190bca801a8a9eecb62 completed May 7, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69fcccee6240819084680887731ff64b completed May 7, 2026, 5:33 p.m.
Created at: May 1, 2026, 1:52 a.m.