Triple

T30617555
Position Surface form Disambiguated ID Type / Status
Subject Gilgal E779353 entity
Predicate traditionallyLocatedNear P59161 FINISHED
Object Jericho 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: Jericho | Statement: [Gilgal, traditionallyLocatedNear, Jericho]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionallyLocatedNear
Context triple: [Gilgal, traditionallyLocatedNear, Jericho]
  • A. historicallyLocatedNear
    Indicates that, in a historical context, one entity was geographically situated close to another entity.
  • B. oftenLocatedNear
    Indicates that one entity is frequently found in close physical proximity to another entity.
  • C. hasLocationTraditionallyIdentifiedAs
    Indicates that something is situated in, or associated with, a place that is customarily or historically recognized as its location, even if this identification is not formally verified.
  • D. traditionallyIdentifiedNear chosen
    Indicates that one entity is customarily or historically regarded as being located close to another entity, based on tradition rather than precise or contemporary evidence.
  • E. traditionallyFoundIn
    Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
  • F. None of above.

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_69f224a3307081909a6dca8ca75dbf48 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fdec5ffe088190ac5505f26c6cff18 completed May 8, 2026, 2 p.m.
PD Predicate disambiguation batch_69fdeae15f1c81908fc63fbc1b028d2e completed May 8, 2026, 1:53 p.m.
Created at: April 29, 2026, 8:26 p.m.