Triple

T21652404
Position Surface form Disambiguated ID Type / Status
Subject Brazilian semi-arid region E534369 entity
Predicate hasCity P316 FINISHED
Object Sobral 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: Sobral | Statement: [Brazilian semi-arid region, hasCity, Sobral]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sobral
Context triple: [Brazilian semi-arid region, hasCity, Sobral]
  • A. Sobral chosen
    Sobral is a historic city in northeastern Brazil known for its cultural heritage and as the site of key observations confirming Einstein’s theory of general relativity during the 1919 solar eclipse.
  • B. Wezep
    Wezep is a village in the Dutch province of Gelderland, known for its location along the railway line between Utrecht and Zwolle.
  • C. Saquarema
    Saquarema is a coastal city in the state of Rio de Janeiro, Brazil, known for its beaches and strong surfing culture.
  • D. Bemposta
    Bemposta is a civil parish located within the municipality of Abrantes in central Portugal.
  • E. Cantanhede
    Cantanhede is a Portuguese municipality in the Centro Region known for its wine production, agricultural activity, and proximity to the Atlantic coast.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c466aec88190ba39c7543dbc8ba2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef591594a08190bf0ddd0a0c0922ba completed April 27, 2026, 12:39 p.m.
Created at: April 16, 2026, 6:36 p.m.