Triple

T13846432
Position Surface form Disambiguated ID Type / Status
Subject Hron River E332816 entity
Predicate nameVariant P744 FINISHED
Object Garam E941857 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: Garam | Statement: [Hron River, nameVariant, Garam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Garam
Context triple: [Hron River, nameVariant, Garam]
  • A. Garam chosen
    Garam is a significant Central European river, known in Slovak as the Hron, that flows through Slovakia before joining the Danube.
  • B. Gahal
    Gahal was a right-wing political alliance in Israel formed in the 1960s, primarily uniting the Herut movement with the Liberal Party and serving as a key predecessor to the Likud party.
  • C. Gurma
    Gurma is a Gur language spoken primarily by the Gurma people in parts of Burkina Faso, Togo, Benin, and neighboring West African countries.
  • D. Tarama
    Tarama is a small island municipality in Okinawa Prefecture, Japan, known for its subtropical climate, traditional Ryukyuan culture, and surrounding coral reefs.
  • E. Gashmu
    Gashmu is an alternate name for Geshem the Arab, a regional leader mentioned in the Hebrew Bible as an opponent of Nehemiah’s efforts to rebuild Jerusalem’s walls.
  • 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_69d81c5ba13c8190839315f54768acfd completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02b1a25c8190a9f85ba43c421188 completed April 14, 2026, 9:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c0ef9e7c8190b96c2b83d04708e1 completed May 3, 2026, 9:41 p.m.
Created at: April 9, 2026, 10:13 p.m.