Triple
T31248873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | בלהה |
E796759
|
entity |
| Predicate | נזכרת ב |
P12313
|
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.
recalledBy
Indicates that an entity is brought back, retrieved, or remembered as a result of another entity’s action or prompting.
-
B.
recalledIn
chosen
Indicates that an entity is mentioned, remembered, or brought up again within a specific context, such as a document, conversation, or event.
-
C.
rememberedThrough
Indicates that one entity is remembered, commemorated, or kept in memory by means of, or through the influence of, another entity or medium.
-
D.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
-
E.
isRememberedOn
Indicates that an entity is commemorated, recalled, or honored on a specific date or occasion.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:11 p.m.