Triple

T12776309
Position Surface form Disambiguated ID Type / Status
Subject Burbank–Santa Rosa E305382 entity
Predicate servesCity P82 FINISHED
Object Santa Rosa, California E27583 NE 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: Santa Rosa, California | Statement: [Burbank–Santa Rosa, servesCity, Santa Rosa, California]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Santa Rosa, California
Context triple: [Burbank–Santa Rosa, servesCity, Santa Rosa, California]
  • A. Santa Rosa
    Santa Rosa is the principal city and administrative center of Argentina’s La Pampa Province, known for its role as a regional hub in the country’s central plains.
  • B. Santa Rosa
    Santa Rosa is a coastal city in southwestern Ecuador known for its agriculture, shrimp farming, and role as a commercial center in El Oro Province.
  • C. Santa Rosa chosen
    Santa Rosa is a mid-sized city in Sonoma County known as a cultural and economic hub of California’s wine country.
  • D. Santa Rosa
    Santa Rosa is a residential barrio (neighborhood) within the municipality of Dorado, Puerto Rico.
  • E. Santa Rosa
    Santa Rosa is a small settlement located on Santa Cruz Island in the Galápagos archipelago of Ecuador.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d7bdf2b43c819098ae5aa68e61ea58 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96df6b3c88190b0bbe70de8ddcbf3 completed April 10, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69b90ae688190b22e3a68d27b54c5 completed May 3, 2026, 12:49 a.m.
Created at: April 9, 2026, 5:29 p.m.