Triple
T36781671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | סיירת מטכ"ל |
E908784
|
entity |
| Predicate | שייכות היסטורית |
P5057
|
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.
historicalHeir
Indicates that one entity is recognized as the successor or inheritor of another in a historical or dynastic context.
-
B.
الأصل التاريخي
Indicates the historical origin or source from which something or someone is derived.
-
C.
الدور التاريخي
Indicates the historical role or function that an entity has played within a particular period, context, or sequence of events.
-
D.
historicallyPartOf
chosen
Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
-
E.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
- 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.