Triple

T9506259
Position Surface form Disambiguated ID Type / Status
Subject Viseu District E229276 entity
Predicate capital P234 FINISHED
Object Viseu E199960 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: Viseu | Statement: [Viseu District, capital, Viseu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Viseu
Context triple: [Viseu District, capital, Viseu]
  • A. Viseu chosen
    Viseu is a historic inland city in central Portugal known for its well-preserved medieval center, wine production, and cultural heritage.
  • B. Sever do Vouga
    Sever do Vouga is a municipality in central Portugal known for its natural landscapes, waterfalls, and rural tourism within the Aveiro District.
  • C. Rio Maior
    Rio Maior is a Portuguese city known for its traditional salt pans and location in the Ribatejo region.
  • D. Golegã
    Golegã is a Portuguese town famed for its equestrian traditions and annual horse fair, located in the Centro Region of Portugal.
  • E. Vira do Minho
    Vira do Minho is a lively traditional Portuguese folk dance from the Minho region, typically performed in circles or pairs to upbeat regional music.
  • 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_69ca847611c48190a28c028644198c75 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9852b7e48190a8f69cbde10d2858 completed April 1, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69d13a1de2d88190a6a10379d2297510 completed April 4, 2026, 4:19 p.m.
Created at: March 30, 2026, 7:57 p.m.