Triple
T1460604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamas |
E31502
|
entity |
| Predicate | tookControlOfGazaIn |
P29034
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Hamas, tookControlOfGazaIn, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookControlOfGazaIn Context triple: [Hamas, tookControlOfGazaIn, 2007]
-
A.
cameUnderIsraeliControl
Indicates that one entity transitioned to being governed, occupied, or administered by Israeli authorities.
-
B.
wasUnderJordanianControl
Indicates that, during a specified time period, the subject entity was governed, administered, or controlled by Jordanian authorities.
-
C.
occupyingPower
Indicates that one entity holds military or political control over a territory that it does not legally own, typically as an occupying authority.
-
D.
regionOnWestBank
Indicates that one region is located on the western bank of another geographic feature, such as a river or body of water.
-
E.
conflictForControlOf
Indicates a struggle or contest between parties to gain dominance, authority, or decision-making power over something.
- F. None of above. chosen
Provenance (4 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59d6dd88190b8ff3bda90aef7e2 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.