Triple

T479905
Position Surface form Disambiguated ID Type / Status
Subject Chicano English E9143 entity
Predicate isRecognizedAs P310 FINISHED
Object legitimate dialect of English 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: legitimate dialect of English | Statement: [Chicano English, isRecognizedAs, legitimate dialect of English]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRecognizedAs
Context triple: [Chicano English, isRecognizedAs, legitimate dialect of English]
  • A. recognizedAs chosen
    Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
  • B. recognizedIn
    Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
  • C. recognizedFor
    Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
  • D. notRecognizedBy
    Indicates that one entity does not acknowledge, accept, or formally recognize the status, authority, or validity of another entity.
  • E. formOfRecognition
    Indicates a relationship where one entity serves as an official acknowledgment, honor, or validation granted to 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_69a2e7ff81708190b0507a24a997232c completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2f057c4ac819080cf43ffaa56c350 completed Feb. 28, 2026, 1:40 p.m.
PD Predicate disambiguation batch_69a2edf1d5848190a7da27e2fddc136f completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.