Triple

T5249288
Position Surface form Disambiguated ID Type / Status
Subject Tajo River E118542 entity
Predicate majorTributary P415 FINISHED
Object Jarama River E77049 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: Jarama River | Statement: [Tajo River, majorTributary, Jarama River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jarama River
Context triple: [Tajo River, majorTributary, Jarama River]
  • A. Jarama River chosen
    The Jarama River is a major tributary of the Tagus in central Spain, historically notable as the site of intense fighting during the Spanish Civil War.
  • B. Henares River
    The Henares River is a tributary of the Jarama in central Spain that flows through Castilla–La Mancha and the Community of Madrid, historically supporting towns such as Alcalá de Henares.
  • C. Manzanares River
    The Manzanares River is a modest river in central Spain that flows through the city of Madrid and has historically shaped its landscape and development.
  • D. Manzanares
    Manzanares is a small Colombian town and municipality located in the mountainous Caldas Department in the Andean region.
  • E. Talavera River
    The Talavera River is a waterway in the Philippines that forms part of the Pampanga River basin in Central Luzon.
  • 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_69bd4468aacc8190a8196f71855cdf4f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7b787b34819081af96de9355bb4f completed March 20, 2026, 4:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf10cdb614819092621690e836338e completed March 21, 2026, 9:42 p.m.
Created at: March 20, 2026, 1:50 p.m.