Triple

T61503
Position Surface form Disambiguated ID Type / Status
Subject Puerto Rican Spanish E1221 entity
Predicate standardBasedOn P1587 FINISHED
Object general Latin American Spanish orthographic norms 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: general Latin American Spanish orthographic norms | Statement: [Puerto Rican Spanish, standardBasedOn, general Latin American Spanish orthographic norms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: standardBasedOn
Context triple: [Puerto Rican Spanish, standardBasedOn, general Latin American Spanish orthographic norms]
  • A. standardType
    Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
  • B. standardizedBy
    Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
  • C. usesStandard chosen
    Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
  • D. basedOnEvent
    Indicates that something is derived from, influenced by, or determined in reference to a specific event.
  • E. notableStandard
    Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
  • 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_69a24ba4f760819081f6638a3c70538a completed Feb. 28, 2026, 1:57 a.m.
NER Named-entity recognition batch_69a251f74b0881909ad89127b8171277 completed Feb. 28, 2026, 2:24 a.m.
PD Predicate disambiguation batch_69a24ea242c8819086fe00bf01e6523e completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:02 a.m.