Triple

T26102794
Position Surface form Disambiguated ID Type / Status
Subject Puerto Rican-Venezuelan American E658457 entity
Predicate regionCommonlyFound P12445 FINISHED
Object East Coast of the United States NE NERFINISHED

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: East Coast of the United States | Statement: [Puerto Rican-Venezuelan American, regionCommonlyFound, East Coast of the United States]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionCommonlyFound
Context triple: [Puerto Rican-Venezuelan American, regionCommonlyFound, East Coast of the United States]
  • A. foundInRegion
    Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
  • B. regionallyAssociatedWith chosen
    Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
  • C. isOftenLocatedAround
    Indicates that one entity is frequently found in the vicinity of, or surrounding, another entity.
  • D. traditionallyFoundIn
    Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
  • E. commonlyFoundOn
    Indicates that one entity is typically or frequently located on, attached to, or present upon 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_69ee5bc09c288190bc42a11972841383 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f6d0d46aec819091edf97324d793ac completed May 3, 2026, 4:36 a.m.
PD Predicate disambiguation batch_69f6cfe2183481908ae4e85a59c66f69 completed May 3, 2026, 4:32 a.m.
Created at: April 26, 2026, 7:56 p.m.