Triple
T36781675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | סיירת מטכ"ל |
E908784
|
entity |
| Predicate | סוג לוחמים |
P33638
|
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.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
eraOfWarfare
Indicates a historical period characterized by significant or sustained warfare.
-
C.
combatArm
chosen
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
D.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
E.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f71e70819089f722234376df65 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.