Triple
T24406761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | דָּוִד אֶלְעָזָר |
E615330
|
entity |
| Predicate | היה חלק מ |
P35
|
FINISHED |
| Object | הנהגת מערכת הביטחון הישראלית בשנות ה-70 |
—
|
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: הנהגת מערכת הביטחון הישראלית בשנות ה-70 | Statement: [דָּוִד אֶלְעָזָר, היה חלק מ, הנהגת מערכת הביטחון הישראלית בשנות ה-70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: היה חלק מ Context triple: [דָּוִד אֶלְעָזָר, היה חלק מ, הנהגת מערכת הביטחון הישראלית בשנות ה-70]
-
A.
hasPartInLife
Indicates that an entity participates in, contributes to, or plays a role within some aspect or period of another entity’s life.
-
B.
hasPart
chosen
Indicates that one entity is a component, segment, or constituent part of another entity.
-
C.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
D.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
E.
has part in role
Indicates that an entity participates as a component or constituent specifically in a defined role within a larger whole or process.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294dfd8d88190b831b6a8f4157980 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.