Triple
T4970055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinchas Menachem Singer |
E111625
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Pinchas |
E400231
|
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: Pinchas | Statement: [Pinchas Menachem Singer, givenName, Pinchas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pinchas Context triple: [Pinchas Menachem Singer, givenName, Pinchas]
-
A.
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.
-
B.
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.
-
C.
Nadab
Nadab is a biblical figure, the eldest son of Aaron who served as a priest during the Israelites’ wilderness period.
-
D.
Shmuel
Shmuel is the Hebrew form of the biblical name Samuel, commonly used in Jewish religious and cultural contexts.
-
E.
Aharon
Aharon is a masculine given name of Hebrew origin, traditionally associated with the biblical figure Aaron and widely used in Jewish communities.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd721221b88190916feb9b4f049195 |
completed | March 20, 2026, 4:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be81f749fc8190ad4dc68f7e2086b1 |
completed | March 21, 2026, 11:33 a.m. |
Created at: March 20, 2026, 1:33 p.m.