Triple
T23258329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbi Pinchas of Koretz |
E581933
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Pinchas |
—
|
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: Pinchas | Statement: [Rabbi Pinchas of Koretz, givenName, Pinchas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pinchas Context triple: [Rabbi Pinchas of Koretz, givenName, Pinchas]
-
A.
Phinehas
Phinehas is a biblical figure known as one of the corrupt priestly sons of Eli who served at the sanctuary in Shiloh.
-
B.
Phinehas
chosen
Phinehas is a biblical priest and grandson of Aaron, noted for his zealous defense of Israel’s covenant with God in the Hebrew Bible.
-
C.
Elazar
Elazar is an Israeli settlement in the Gush Etzion bloc in the West Bank, known primarily as a residential community for Jewish Israelis.
-
D.
Nadab
Nadab was a king of the northern Kingdom of Israel in the Hebrew Bible, known as the son and short-reigning royal heir of Jeroboam I.
-
E.
Nadab
Nadab is a biblical figure, the eldest son of Aaron who served as a priest during the Israelites’ wilderness period.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c710c48190aff03d210642a043 |
completed | April 29, 2026, 5:19 a.m. |
Created at: April 17, 2026, 4:11 p.m.