Triple

T3001348
Position Surface form Disambiguated ID Type / Status
Subject Yahwism E81793 entity
Predicate cultCenter P9995 FINISHED
Object Bethel E233623 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: Bethel | Statement: [Yahwism, cultCenter, Bethel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bethel
Context triple: [Yahwism, cultCenter, Bethel]
  • A. Bethel
    Bethel is a remote city in western Alaska that serves as a regional hub for transportation, health care, and services for many surrounding Yup’ik villages.
  • B. Bethel chosen
    Bethel was an important religious and political center in ancient Israel, traditionally associated with patriarchal worship and later Israelite monarchy.
  • C. Bethel, Connecticut
    Bethel, Connecticut is a suburban New England town in Fairfield County known for its historic downtown and role as a residential community near Danbury.
  • D. Farmington
    Farmington is a city in northwestern New Mexico known as a regional hub for energy production and outdoor recreation near the Four Corners area.
  • E. Belhaven
    Belhaven is a small community located within the town of Georgina in Ontario, Canada.
  • 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a11b4bc81909ce06121361b4e0f completed March 8, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b12e4b54188190bf900bf10061a57a completed March 11, 2026, 8:56 a.m.
Created at: March 8, 2026, 2:59 p.m.