Triple

T21183796
Position Surface form Disambiguated ID Type / Status
Subject Tambre River E522022 entity
Predicate near P350 FINISHED
Object A Coruña 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: A Coruña | Statement: [Tambre River, near, A Coruña]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A Coruña
Context triple: [Tambre River, near, A Coruña]
  • A. A Coruña chosen
    A Coruña is a coastal city in northwestern Spain known for its historic lighthouse, the Tower of Hercules, and its role as an important cultural and economic center in the region.
  • B. Pontevedra
    Pontevedra is a coastal municipality in the province of Capiz in the Philippines, known for its fishing communities and agricultural economy.
  • C. Pontevedra
    Pontevedra is a coastal province in northwestern Spain known for its historic towns, Atlantic landscapes, and location within the autonomous community of Galicia.
  • D. Ferrol
    Ferrol is a coastal city and major naval shipbuilding center in the Galicia region of northwestern Spain.
  • E. Ferrol
    Ferrol is a coastal municipality located on Tablas Island in the province of Romblon in the Philippines.
  • 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_69e0b50ef1d48190b063aa342667df22 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7301f7f1c81908686866fdee57127 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 3:05 p.m.