Triple
T26027208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | מחוז הדרום |
E647324
|
entity |
| Predicate | כולל אוכלוסייה יהודית |
P96191
|
FINISHED |
| Object | כן |
—
|
LITERAL 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: כן | Statement: [מחוז הדרום, כולל אוכלוסייה יהודית, כן]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: כולל אוכלוסייה יהודית Context triple: [מחוז הדרום, כולל אוכלוסייה יהודית, כן]
-
A.
hasSignificantJewishCommunity
Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
-
B.
כולל
chosen
Indicates that something contains, includes, or encompasses something else as a part or subset.
-
C.
eraWithinJudaism
Indicates that a time period or era occurs within, or is defined as part of, the broader historical or religious framework of Judaism.
-
D.
judaismView
Indicates a relationship where one entity holds a particular view, interpretation, or doctrinal position within or about Judaism regarding another entity or topic.
-
E.
hasJewishDenomination
Indicates that an entity is associated with, or belongs to, a specific Jewish religious denomination or movement.
- F. None of above.
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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 22, 2026, 9:05 a.m.