Triple

T22803788
Position Surface form Disambiguated ID Type / Status
Subject Efrem E564473 entity
Predicate relatedName P3889 FINISHED
Object Ephraim E148887 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: Ephraim | Statement: [Efrem, relatedName, Ephraim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ephraim
Context triple: [Efrem, relatedName, Ephraim]
  • A. Ephraim
    Ephraim is a small, historic village and popular tourist destination on the shores of Green Bay in Door County, Wisconsin.
  • B. Ephraim chosen
    Ephraim is one of the tribes of Israel, traditionally descended from Joseph’s younger son and known for its prominence in the northern kingdom.
  • C. Bene Ephraim
    Bene Ephraim are a small Telugu-speaking community in India that identifies as Jewish, tracing their origins to ancient Israelite ancestry and practicing a form of Judaism blended with local traditions.
  • D. Elizur
    Elizur is a masculine given name of Hebrew origin, historically borne by several notable figures in early American history.
  • E. Zabulon
    Zabulon is a variant form of the biblical given name Zebulun, traditionally associated with one of the twelve tribes of Israel.
  • 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_69e245823f4c8190ade442cdcc2c224a completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17d5a7c2881909a7aaacddd09f00c completed April 29, 2026, 3:39 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0b9e9b35e08190a3ad478355279253 completed May 18, 2026, 11:19 p.m.
Created at: April 17, 2026, 3:31 p.m.