Triple
T35849849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | רצועת עזה |
E1036317
|
entity |
| Predicate | הייתה תחת |
P167397
|
FINISHED |
| Object | ממשל צבאי ישראלי לאחר 1967 |
—
|
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: ממשל צבאי ישראלי לאחר 1967 | Statement: [רצועת עזה, הייתה תחת, ממשל צבאי ישראלי לאחר 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: הייתה תחת Context triple: [רצועת עזה, הייתה תחת, ממשל צבאי ישראלי לאחר 1967]
-
A.
הייתה בה
Indicates that something existed, was present, or was contained within something (typically a place, object, or situation).
-
B.
הייתה תחת כיבוש
chosen
Indicates that one entity was under the military or political occupation or control of another entity.
-
C.
הייתה בעבר
Indicates that an entity existed or held a certain state, role, or property in the past but not necessarily in the present.
-
D.
wasBelow
Indicates that one entity was positioned at a lower level or altitude than another entity at a given time.
-
E.
wasHeldUnder
Indicates that an event, activity, or state took place while being subject to the authority, control, jurisdiction, or auspices of a particular entity or condition.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.