Triple

T14854885
Position Surface form Disambiguated ID Type / Status
Subject Ginosar E349325 entity
Predicate locatedNear P294 FINISHED
Object Tiberias E2296 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: Tiberias | Statement: [Ginosar, locatedNear, Tiberias]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tiberias
Context triple: [Ginosar, locatedNear, Tiberias]
  • A. Tiberias chosen
    Tiberias is an ancient city in northern Israel on the western shore of the Sea of Galilee, historically significant as a major center of Jewish learning and pilgrimage.
  • B. Banias
    Banias is a coastal city on the Mediterranean Sea in western Syria, known for its oil refinery and port facilities.
  • C. Banias
    Banias is an ancient site in the Golan Heights known for its springs, archaeological ruins, and historical sanctuary dedicated to the Greek god Pan.
  • D. Banias
    Banias are a traditional Indian merchant and trading community historically associated with commerce, moneylending, and often with Vaishya caste status.
  • E. الناصرة
    الناصرة مدينة تاريخية في الجليل شمال فلسطين/إسرائيل تُعد من أهم المدن المسيحية لارتباطها بسيرة السيد المسيح.
  • 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_69d822ed7e1881909b90fca143ad7e34 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded44318f0819080b6c599f2d3474f completed April 14, 2026, 11:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe6b4ce76881909bf4a967da9357ae completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 1:54 a.m.