Triple
T25803053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | נגב |
E649887
|
entity |
| Predicate | כולל בסיס צבאי מרכזי |
P149006
|
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.
militaryBasis
Indicates that one entity serves as the foundational military justification, rationale, or underlying military reason for another entity or action.
-
B.
militaryCoreOf
chosen
Indicates that one entity serves as the primary military component, foundation, or central force of another entity.
-
C.
עיר מרכזית קשורה
Indicates a relationship where one city is connected or associated with another city that serves as a central or main city in some defined context.
-
D.
militaryBaseUser
Indicates that one entity uses, operates, or is stationed at a particular military base.
-
E.
militaryBaseContext
Indicates that the relationship or action occurs within, is associated with, or is influenced by a military base setting or operational environment.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ffccd0d0819095d21378b5b9590a |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 6:42 a.m.