Triple
T4368196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinchas Rosen |
E98829
|
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 Rosen, givenName, Pinchas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pinchas Context triple: [Pinchas Rosen, 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.
Shmuel
Shmuel is the Hebrew form of the biblical name Samuel, commonly used in Jewish religious and cultural contexts.
-
C.
Aharon
Aharon is a masculine given name of Hebrew origin, traditionally associated with the biblical figure Aaron and widely used in Jewish communities.
-
D.
Berechiah
Berechiah is a biblical figure mentioned in the Hebrew Bible as part of the priestly and prophetic lineage associated with the prophet Zechariah.
-
E.
Eleazar
Eleazar is a masculine given name of Hebrew origin, traditionally associated with religious and historical figures.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352034d3881909ed4b2f9eef5e823 |
completed | March 12, 2026, 11:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5dbcec90881908fe83c83119d99fe |
completed | March 14, 2026, 10:06 p.m. |
Created at: March 12, 2026, 11:17 p.m.